Alloy: спампаваць старыя версіі

This is release v1.11.3 of Grafana Alloy.
Upgrading
Read the release notes for specific instructions on upgrading from older versions:
Notable changes:
Enhancements
- Schedule new path targets faster in loki.source.file. (@kalleep)
- Add prometheus.static.exporter that exposes metrics specified in a text file in Prometheus exposition format. (@kalleep)
Bugfixes
- local.file_match now publish targets faster whenever targets in arguments changes. (@kalleep)
- Fix otelcol.exporter.splunkhec arguments missing documented otel_attrs_to_hec_metadata block. (@dehaansa)
- Support Scrape Protocol specification in CRDS for prometheus.operator.* components. (@dehaansa)
- Fix panic in otelcol.receiver.syslog when no tcp block was configured. (@kalleep)
For a full list of changes, please refer to the CHANGELOG!
Installation
Refer to our installation guide for how to install Grafana Alloy.

Notable changes:
Breaking changes
- Prometheus dependency had a major version upgrade from v2.55.1 to v3.4.2. (@thampiotr)
- The . pattern in regular expressions in PromQL matches newline characters now. With this change a regular expressions like .* matches strings that include \n. This applies to matchers in queries and relabel configs in Prometheus and Loki components.
- The enable_http2 in prometheus.remote_write component's endpoints has been changed to false by default. Previously, in Prometheus v2 the remote write http client would default to use http2. In order to parallelize multiple remote write queues across multiple sockets its preferable to not default to http2. If you prefer to use http2 for remote write you must now set enable_http2 to true in your prometheus.remote_write endpoints configuration section.
- The experimental CLI flag --feature.prometheus.metric-validation-scheme has been deprecated and has no effect. You can configure the metric validation scheme individually for each prometheus.scrape component.
- Log message format has changed for some of the prometheus.* components as part of the upgrade to Prometheus v3.
- The values of the le label of classic histograms and the quantile label of summaries are now normalized upon ingestion. In previous Alloy versions, that used Prometheus v2, the value of these labels depended on the scrape protocol (protobuf vs text format) in some situations. This led to label values changing based on the scrape protocol. E.g. a metric exposed as my_classic_hist{le="1"} would be ingested as my_classic_hist{le="1"} via the text format, but as my_classic_hist{le="1.0"} via protobuf. This changed the identity of the metric and caused problems when querying the metric. In current Alloy release, which uses Prometheus v3, these label values will always be normalized to a float like representation. I.e. the above example will always result in my_classic_hist{le="1.0"} being ingested into Prometheus, no matter via which protocol. The effect of this change is that alerts, recording rules and dashboards that directly reference label values as whole numbers such as le="1" will stop working.
The recommended way to deal with this change is to fix references to integer le and quantile label values, but otherwise do nothing and accept that some queries that span the transition time will produce inaccurate or unexpected results.
See the upstream Prometheus v3 migration guide for more details.
- prometheus.exporter.windows dependency has been updated to v0.31.1. (@dehaansa)
- There are various renamed metrics and two removed collectors (cs, logon).
- scrape_native_histograms attribute for prometheus.scrape is now set to false, whereas in previous versions of Alloy it would default to true. This means that it is no longer enough to just configure scrape_protocols to start with PrometheusProto to scrape native histograms - scrape_native_histograms has to be enabled. If scrape_native_histograms is enabled, scrape_protocols will automatically be configured correctly for you to include PrometheusProto. If you configure it explicitly, Alloy will validate that PrometheusProto is in the scrape_protocols list.
- Add otel_attrs_to_hec_metadata configuration block to otelcol.exporter.splunkhec to match otelcol.receiver.splunkhec. (@cgetzen)
- [otelcol.processor.batch] Two arguments have different default values. (@ptodev)
- send_batch_size is now set to 2000 by default. It used to be 8192.
- send_batch_max_size is now set to 3000 by default. It used to be 0.
- This helps prevent issues with ingestion of batches that are too large.
- OpenTelemetry Collector dependencies upgraded from v0.128.0 to v0.134.0. (@ptodev)
- The otelcol.receiver.opencensus component has been deprecated and will be removed in a future release, use otelcol.receiver.otelp instead.
- [otelcol.exporter.*] The deprecated blocking argument in the sending_queue block has been removed.
Use block_on_overflow instead.
- [otelcol.receiver.