homelab/ansible-collection
0
0
Fork 0
Code Issues 1 Pull requests 1 Releases 159 Activity Actions

chore(deps): update dependency grafana/alloy to v1.11.0 #110

Merged
GregoryDosh merged 1 commit from renovate/grafana-alloy-1.x into main 2025-10-01 03:25:15 +00:00
Conversation 0 Commits 1 Files changed 1 +1 -1
svc-renovate-bot commented 2025-10-01 00:34:26 +00:00
Member
Copy link

This PR contains the following updates:

Package Update Change
grafana/alloy minor 1.10.2 -> 1.11.0

Release Notes

grafana/alloy (grafana/alloy)

v1.11.0

Compare Source

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), see the v1.11 release notes for more information.

  • 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.kafka, otelcol.exporter.kafka]: Removed the broker_addr argument from the aws_msk block.
      Also removed the SASL/AWS_MSK_IAM authentication mechanism.
    • [otelcol.exporter.splunkhec] The batcher block is deprecated and will be removed in a future release. Use the queue block instead.
    • [otelcol.exporter.loadbalancing] Use a linear probe to decrease variance caused by hash collisions, which was causing a non-uniform distribution of loadbalancing.
    • [otelcol.connector.servicegraph] The database_name_attribute argument has been removed.
    • [otelcol.connector.spanmetrics] Adds a default maximum number of exemplars within the metric export interval.
    • [otelcol.processor.tail_sampling] Add a new block_on_overflow config attribute.
Features

  • Add the otelcol.receiver.fluentforward receiver to receive logs via Fluent Forward Protocol. (@​rucciva)

  • Add the prometheus.enrich component to enrich metrics using labels from discovery.* components. (@​ArkovKonstantin)

  • Add node_filter configuration block to loki.source.podlogs component to enable node-based filtering for pod discovery. When enabled, only pods running on the specified node will be discovered and monitored, significantly reducing API server load and network traffic in DaemonSet deployments. (@​QuentinBisson)

  • (Experimental) Additions to experimental database_observability.mysql component:

    • query_sample collector now supports auto-enabling the necessary setup_consumers settings (@​cristiangreco)
    • query_sample collector is now compatible with mysql less than 8.0.28 (@​cristiangreco)
    • include server_id label on log entries (@​matthewnolf)
    • support receiving targets argument and relabel those to include server_id (@​matthewnolf)
    • updated the config blocks and documentation (@​cristiangreco)

  • (Experimental) Additions to experimental database_observability.postgres component:

    • add query_tables collector for postgres (@​matthewnolf)
    • add cloud_provider.aws configuration that enables optionally supplying the ARN of the database under observation. The ARN is appended to metric samples as labels for easier filtering and grouping of resources.
    • add query_sample collector for postgres (@​gaantunes)
    • add schema_details collector for postgres (@​fridgepoet)
    • include server_id label on logs and metrics (@​matthewnolf)

  • Add otelcol.receiver.googlecloudpubsub community component to receive metrics, traces, and logs from Google Cloud Pub/Sub subscription. (@​eraac)

  • Add otel collector converter for otelcol.receiver.googlecloudpubsub. (@​kalleep)

  • (Experimental) Add a honor_metadata configuration argument to the prometheus.scrape component.
    When set to true, it will propagate metric metadata to downstream components.

  • Add a flag to pyroscope.ebpf alloy configuration to set the off-cpu profiling threshold. (@​luweglarz)

  • Add encoding.url_encode and encoding.url_decode std lib functions. (@​kalleep)

Enhancements

  • Ensure text in the UI does not overflow node boundaries in the graph. (@​blewis12)

  • Fix pyroscope.write component's AppendIngest method to respect configured timeout and implement retry logic. The method now properly uses the configured remote_timeout, includes retry logic with exponential backoff, and tracks metrics for sent/dropped bytes and profiles consistently with the Append method. (@​korniltsev)

  • pyroscope.write, pyroscope.receive_http components include trace_id in logs and propagate it downstream. (@​korniltsev)

  • Improve logging in pyroscope.write component. (@​korniltsev)

  • Add comprehensive latency metrics to pyroscope.write component with endpoint-specific tracking for both push and ingest operations. (@​korniltsev, @​claude)

  • prometheus.scrape now supports convert_classic_histograms_to_nhcb, enable_compression, metric_name_validation_scheme, metric_name_escaping_scheme, native_histogram_bucket_limit, and native_histogram_min_bucket_factor arguments. See reference documentation for more details. (@​thampiotr)

  • Add max_send_message_size configuration option to loki.source.api component to control the maximum size of requests to the push API. (@​thampiotr)

  • Add protobuf_message argument to prometheus.remote_write endpoint configuration to support both Prometheus Remote Write v1 and v2 protocols. The default remains "prometheus.WriteRequest" (v1) for backward compatibility. (@​thampiotr)

  • Update the yet-another-cloudwatch-exporter dependency to point to the prometheus-community repo as it has been donated. Adds a few new services to prometheus.exporter.cloudwatch. (@​dehaansa, @​BoweFlex, @​andriikushch)

  • pyroscope.java now supports configuring the log_level and quiet flags on async-profiler. (@​deltamualpha)

  • Add application_host and network_inter_zone features to beyla.ebpf component. (@​marctc)

  • Set the publisher name in the Windows installer to "Grafana Labs". (@​martincostello)

  • Switch to the community maintained fork of go-jmespath that has more features. (@​dehaansa)

  • Add a stage.pattern stage to loki.process that uses LogQL patterns to parse logs. (@​dehaansa)

  • Add support to validate references, stdlib functions and arguments when using validate command. (@​kalleep)

  • Update the prometheus.exporter.process component to get the remove_empty_groups option. (@​dehaansa)

  • Remove unnecessary allocations in stage.static_labels. (@​kalleep)

  • Upgrade beyla.ebpf from Beyla version v2.2.5 to v2.5.8 The full list of changes can be found in the Beyla release notes (@​marctc)

  • prometheus.exporter.azure supports setting interval and timespan independently allowing for further look back when querying metrics. (@​kgeckhart)

  • loki.source.journal now supports legacy_positon block that can be used to translate Static Agent or Promtail position files. (@​kalleep)

  • Normalize attr key name in logfmt logger. (@​zry98)

  • (Experimental) Add an extra parameter to the array.combine_maps standard library function
    to enable preserving the first input list even if there is no match. (@​ptodev)

  • Reduce memory overhead of prometheus.remote_write's WAL by bringing in an upstream change to only track series in a slice if there's a hash conflict. (@​kgeckhart)

  • Reduce log level from warning for loki.write when request fails and will be retried. (@​kalleep)

  • Fix slow updates to loki.source.file when only targets have changed and pipeline is blocked on writes. (@​kalleep)

  • Reduced allocation in loki.write when using external labels with mutliple endpoints. (@​kalleep)

  • The Windows installer and executables are now code signed. (@​martincostello)

  • Reduce compressed request size in prometheus.write.queue by ensuring append order is maintained when sending metrics to the WAL. (@​kgeckhart)

  • Add protobuf_message and metadata_cache_size arguments to prometheus.write.queue endpoint configuration to support both Prometheus Remote Write v1 and v2 protocols. The default remains "prometheus.WriteRequest" (v1) for backward compatibility. (@​dehaansa)

  • Reduce allocations for loki.process when stage.template is used. (@​kalleep)

  • Reduce CPU of prometheus.write.queue by eliminating duplicate calls to calculate the protobuf Size. (@​kgeckhart)

  • Use new cache for metadata cache in prometheus.write.queue and support disabling the metadata cache with it disable by default. (@​kgeckhart, @​dehaansa)

Bugfixes

  • Update webdevops/go-common dependency to resolve concurrent map write panic. (@​dehaansa)

  • Fix ebpf profiler metrics pyroscope_ebpf_active_targets, pyroscope_ebpf_profiling_sessions_total, pyroscope_ebpf_profiling_sessions_failing_total not being updated. (luweglarz)

  • Fix prometheus.operator.podmonitors so it now handle portNumber from PodMonitor CRD. (@​kalleep)

  • Fix pyroscope.receive_http so it does not restart server if the server configuration has not changed. (@​korniltsev)

  • Increase default connection limit in pyroscope.receive_http from 100 to 16k. (@​korniltsev)

  • Fix issue in prometheus.remote_write's WAL which could allow it to hold an active series forever. (@​kgeckhart)

  • Fix issue in static and promtail converter where metrics type was not properly handled. (@​kalleep)

  • Fix prometheus.operator.* components to allow them to scrape correctly Prometheus Operator CRDs. (@​thomas-gouveia)

  • Fix database_observability.mysql and database_observability.postgres crashing alloy process due to uncaught errors.

  • Fix data race inloki.source.docker that could cause Alloy to panic. (@​kalleep)

  • Fix race conditions in loki.source.syslog where it could deadlock or cause port bind errors during config reload or shutdown. (@​thampiotr)

  • Fix prometheus.exporter.redis component so that it no longer ignores the MaxDistinctKeyGroups configuration option. If key group metrics are enabled, this will increase the cardinality of the generated metrics. (@​stegosaurus21)

  • Fix loki.source.podlogs component to properly collect logs from Kubernetes Jobs and CronJobs. Previously, the component would fail to scrape logs from short-lived or terminated jobs due to race conditions between job completion and pod discovery. The fix includes:

    • Job-aware termination logic with extended grace periods (10-60 seconds) to ensure all logs are captured
    • Proper handling of pod deletion and race conditions between job completion and controller cleanup
    • Separation of concerns: shouldStopTailingContainer() handles standard Kubernetes restart policies for regular pods, while shouldStopTailingJobContainer() handles job-specific lifecycle with grace periods
    • Enhanced deduplication mechanisms to prevent duplicate log collection while ensuring comprehensive coverage
    • Comprehensive test coverage including unit tests and deduplication validation
      This resolves the issue where job logs were being missed, particularly for fast-completing jobs or jobs that terminated before discovery. (@​QuentinBisson)

  • Fix loki.source.journal creation failing with an error when the journal file is not found. (@​thampiotr)

  • Fix graph UI so it generates correct URLs for components in remotecfg modules. (@​patrickeasters)

  • Fix panic in loki.write when component is shutting down and external_labels are configured. (@​kalleep)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [grafana/alloy](https://github.com/grafana/alloy) | minor | `1.10.2` -> `1.11.0` | --- ### Release Notes <details> <summary>grafana/alloy (grafana/alloy)</summary> ### [`v1.11.0`](https://github.com/grafana/alloy/blob/HEAD/CHANGELOG.md#v1110) [Compare Source](https://github.com/grafana/alloy/compare/v1.10.2...v1.11.0) ##### Breaking changes - Prometheus dependency had a major version upgrade from v2.55.1 to v3.4.2. ([@&#8203;thampiotr](https://github.com/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](https://prometheus.io/docs/prometheus/3.4/migration/) for more details. - `prometheus.exporter.windows` dependency has been updated to v0.31.1. ([@&#8203;dehaansa](https://github.com/dehaansa)) - There are various renamed metrics and two removed collectors (`cs`, `logon`), see the [v1.11 release notes][1_11-release-notes] for more information. [1_11-release-notes]: https://grafana.com/docs/alloy/latest/release-notes/#v111 - `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`. ([@&#8203;cgetzen](https://github.com/cgetzen)) - \[`otelcol.processor.batch`] Two arguments have different default values. ([@&#8203;ptodev](https://github.com/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. ([@&#8203;ptodev](https://github.com/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.kafka`, `otelcol.exporter.kafka`]: Removed the `broker_addr` argument from the `aws_msk` block. Also removed the `SASL/AWS_MSK_IAM` authentication mechanism. - \[`otelcol.exporter.splunkhec`] The `batcher` block is deprecated and will be removed in a future release. Use the `queue` block instead. - \[`otelcol.exporter.loadbalancing`] Use a linear probe to decrease variance caused by hash collisions, which was causing a non-uniform distribution of loadbalancing. - \[`otelcol.connector.servicegraph`] The `database_name_attribute` argument has been removed. - \[`otelcol.connector.spanmetrics`] Adds a default maximum number of exemplars within the metric export interval. - \[`otelcol.processor.tail_sampling`] Add a new `block_on_overflow` config attribute. ##### Features - Add the `otelcol.receiver.fluentforward` receiver to receive logs via Fluent Forward Protocol. ([@&#8203;rucciva](https://github.com/rucciva)) - Add the `prometheus.enrich` component to enrich metrics using labels from `discovery.*` components. ([@&#8203;ArkovKonstantin](https://github.com/ArkovKonstantin)) - Add `node_filter` configuration block to `loki.source.podlogs` component to enable node-based filtering for pod discovery. When enabled, only pods running on the specified node will be discovered and monitored, significantly reducing API server load and network traffic in DaemonSet deployments. ([@&#8203;QuentinBisson](https://github.com/QuentinBisson)) - (*Experimental*) Additions to experimental `database_observability.mysql` component: - `query_sample` collector now supports auto-enabling the necessary `setup_consumers` settings ([@&#8203;cristiangreco](https://github.com/cristiangreco)) - `query_sample` collector is now compatible with mysql less than 8.0.28 ([@&#8203;cristiangreco](https://github.com/cristiangreco)) - include `server_id` label on log entries ([@&#8203;matthewnolf](https://github.com/matthewnolf)) - support receiving targets argument and relabel those to include `server_id` ([@&#8203;matthewnolf](https://github.com/matthewnolf)) - updated the config blocks and documentation ([@&#8203;cristiangreco](https://github.com/cristiangreco)) - (*Experimental*) Additions to experimental `database_observability.postgres` component: - add `query_tables` collector for postgres ([@&#8203;matthewnolf](https://github.com/matthewnolf)) - add `cloud_provider.aws` configuration that enables optionally supplying the ARN of the database under observation. The ARN is appended to metric samples as labels for easier filtering and grouping of resources. - add `query_sample` collector for postgres ([@&#8203;gaantunes](https://github.com/gaantunes)) - add `schema_details` collector for postgres ([@&#8203;fridgepoet](https://github.com/fridgepoet)) - include `server_id` label on logs and metrics ([@&#8203;matthewnolf](https://github.com/matthewnolf)) - Add `otelcol.receiver.googlecloudpubsub` community component to receive metrics, traces, and logs from Google Cloud Pub/Sub subscription. ([@&#8203;eraac](https://github.com/eraac)) - Add otel collector converter for `otelcol.receiver.googlecloudpubsub`. ([@&#8203;kalleep](https://github.com/kalleep)) - (*Experimental*) Add a `honor_metadata` configuration argument to the `prometheus.scrape` component. When set to `true`, it will propagate metric metadata to downstream components. - Add a flag to pyroscope.ebpf alloy configuration to set the off-cpu profiling threshold. ([@&#8203;luweglarz](https://github.com/luweglarz)) - Add `encoding.url_encode` and `encoding.url_decode` std lib functions. ([@&#8203;kalleep](https://github.com/kalleep)) ##### Enhancements - Ensure text in the UI does not overflow node boundaries in the graph. ([@&#8203;blewis12](https://github.com/blewis12)) - Fix `pyroscope.write` component's `AppendIngest` method to respect configured timeout and implement retry logic. The method now properly uses the configured `remote_timeout`, includes retry logic with exponential backoff, and tracks metrics for sent/dropped bytes and profiles consistently with the `Append` method. ([@&#8203;korniltsev](https://github.com/korniltsev)) - `pyroscope.write`, `pyroscope.receive_http` components include `trace_id` in logs and propagate it downstream. ([@&#8203;korniltsev](https://github.com/korniltsev)) - Improve logging in `pyroscope.write` component. ([@&#8203;korniltsev](https://github.com/korniltsev)) - Add comprehensive latency metrics to `pyroscope.write` component with endpoint-specific tracking for both push and ingest operations. ([@&#8203;korniltsev](https://github.com/korniltsev), [@&#8203;claude](https://github.com/claude)) - `prometheus.scrape` now supports `convert_classic_histograms_to_nhcb`, `enable_compression`, `metric_name_validation_scheme`, `metric_name_escaping_scheme`, `native_histogram_bucket_limit`, and `native_histogram_min_bucket_factor` arguments. See reference documentation for more details. ([@&#8203;thampiotr](https://github.com/thampiotr)) - Add `max_send_message_size` configuration option to `loki.source.api` component to control the maximum size of requests to the push API. ([@&#8203;thampiotr](https://github.com/thampiotr)) - Add `protobuf_message` argument to `prometheus.remote_write` endpoint configuration to support both Prometheus Remote Write v1 and v2 protocols. The default remains `"prometheus.WriteRequest"` (v1) for backward compatibility. ([@&#8203;thampiotr](https://github.com/thampiotr)) - Update the `yet-another-cloudwatch-exporter` dependency to point to the prometheus-community repo as it has been donated. Adds a few new services to `prometheus.exporter.cloudwatch`. ([@&#8203;dehaansa](https://github.com/dehaansa), [@&#8203;BoweFlex](https://github.com/BoweFlex), [@&#8203;andriikushch](https://github.com/andriikushch)) - `pyroscope.java` now supports configuring the `log_level` and `quiet` flags on async-profiler. ([@&#8203;deltamualpha](https://github.com/deltamualpha)) - Add `application_host` and `network_inter_zone` features to `beyla.ebpf` component. ([@&#8203;marctc](https://github.com/marctc)) - Set the publisher name in the Windows installer to "Grafana Labs". ([@&#8203;martincostello](https://github.com/martincostello)) - Switch to the community maintained fork of `go-jmespath` that has more features. ([@&#8203;dehaansa](https://github.com/dehaansa)) - Add a `stage.pattern` stage to `loki.process` that uses LogQL patterns to parse logs. ([@&#8203;dehaansa](https://github.com/dehaansa)) - Add support to validate references, stdlib functions and arguments when using validate command. ([@&#8203;kalleep](https://github.com/kalleep)) - Update the `prometheus.exporter.process` component to get the `remove_empty_groups` option. ([@&#8203;dehaansa](https://github.com/dehaansa)) - Remove unnecessary allocations in `stage.static_labels`. ([@&#8203;kalleep](https://github.com/kalleep)) - Upgrade `beyla.ebpf` from Beyla version v2.2.5 to v2.5.8 The full list of changes can be found in the [Beyla release notes](https://github.com/grafana/beyla/releases/tag/v2.5.2) ([@&#8203;marctc](https://github.com/marctc)) - `prometheus.exporter.azure` supports setting `interval` and `timespan` independently allowing for further look back when querying metrics. ([@&#8203;kgeckhart](https://github.com/kgeckhart)) - `loki.source.journal` now supports `legacy_positon` block that can be used to translate Static Agent or Promtail position files. ([@&#8203;kalleep](https://github.com/kalleep)) - Normalize attr key name in logfmt logger. ([@&#8203;zry98](https://github.com/zry98)) - (*Experimental*) Add an extra parameter to the `array.combine_maps` standard library function to enable preserving the first input list even if there is no match. ([@&#8203;ptodev](https://github.com/ptodev)) - Reduce memory overhead of `prometheus.remote_write`'s WAL by bringing in an upstream change to only track series in a slice if there's a hash conflict. ([@&#8203;kgeckhart](https://github.com/kgeckhart)) - Reduce log level from warning for `loki.write` when request fails and will be retried. ([@&#8203;kalleep](https://github.com/kalleep)) - Fix slow updates to `loki.source.file` when only targets have changed and pipeline is blocked on writes. ([@&#8203;kalleep](https://github.com/kalleep)) - Reduced allocation in `loki.write` when using external labels with mutliple endpoints. ([@&#8203;kalleep](https://github.com/kalleep)) - The Windows installer and executables are now code signed. ([@&#8203;martincostello](https://github.com/martincostello)) - Reduce compressed request size in `prometheus.write.queue` by ensuring append order is maintained when sending metrics to the WAL. ([@&#8203;kgeckhart](https://github.com/kgeckhart)) - Add `protobuf_message` and `metadata_cache_size` arguments to `prometheus.write.queue` endpoint configuration to support both Prometheus Remote Write v1 and v2 protocols. The default remains `"prometheus.WriteRequest"` (v1) for backward compatibility. ([@&#8203;dehaansa](https://github.com/dehaansa)) - Reduce allocations for `loki.process` when `stage.template` is used. ([@&#8203;kalleep](https://github.com/kalleep)) - Reduce CPU of `prometheus.write.queue` by eliminating duplicate calls to calculate the protobuf Size. ([@&#8203;kgeckhart](https://github.com/kgeckhart)) - Use new cache for metadata cache in `prometheus.write.queue` and support disabling the metadata cache with it disable by default. ([@&#8203;kgeckhart](https://github.com/kgeckhart), [@&#8203;dehaansa](https://github.com/dehaansa)) ##### Bugfixes - Update `webdevops/go-common` dependency to resolve concurrent map write panic. ([@&#8203;dehaansa](https://github.com/dehaansa)) - Fix ebpf profiler metrics `pyroscope_ebpf_active_targets`, `pyroscope_ebpf_profiling_sessions_total`, `pyroscope_ebpf_profiling_sessions_failing_total` not being updated. (luweglarz) - Fix `prometheus.operator.podmonitors` so it now handle portNumber from PodMonitor CRD. ([@&#8203;kalleep](https://github.com/kalleep)) - Fix `pyroscope.receive_http` so it does not restart server if the server configuration has not changed. ([@&#8203;korniltsev](https://github.com/korniltsev)) - Increase default connection limit in `pyroscope.receive_http` from 100 to 16k. ([@&#8203;korniltsev](https://github.com/korniltsev)) - Fix issue in `prometheus.remote_write`'s WAL which could allow it to hold an active series forever. ([@&#8203;kgeckhart](https://github.com/kgeckhart)) - Fix issue in static and promtail converter where metrics type was not properly handled. ([@&#8203;kalleep](https://github.com/kalleep)) - Fix `prometheus.operator.*` components to allow them to scrape correctly Prometheus Operator CRDs. ([@&#8203;thomas-gouveia](https://github.com/thomas-gouveia)) - Fix `database_observability.mysql` and `database_observability.postgres` crashing alloy process due to uncaught errors. - Fix data race in`loki.source.docker` that could cause Alloy to panic. ([@&#8203;kalleep](https://github.com/kalleep)) - Fix race conditions in `loki.source.syslog` where it could deadlock or cause port bind errors during config reload or shutdown. ([@&#8203;thampiotr](https://github.com/thampiotr)) - Fix `prometheus.exporter.redis` component so that it no longer ignores the `MaxDistinctKeyGroups` configuration option. If key group metrics are enabled, this will increase the cardinality of the generated metrics. ([@&#8203;stegosaurus21](https://github.com/stegosaurus21)) - **Fix `loki.source.podlogs` component to properly collect logs from Kubernetes Jobs and CronJobs.** Previously, the component would fail to scrape logs from short-lived or terminated jobs due to race conditions between job completion and pod discovery. The fix includes: - Job-aware termination logic with extended grace periods (10-60 seconds) to ensure all logs are captured - Proper handling of pod deletion and race conditions between job completion and controller cleanup - Separation of concerns: `shouldStopTailingContainer()` handles standard Kubernetes restart policies for regular pods, while `shouldStopTailingJobContainer()` handles job-specific lifecycle with grace periods - Enhanced deduplication mechanisms to prevent duplicate log collection while ensuring comprehensive coverage - Comprehensive test coverage including unit tests and deduplication validation This resolves the issue where job logs were being missed, particularly for fast-completing jobs or jobs that terminated before discovery. ([@&#8203;QuentinBisson](https://github.com/QuentinBisson)) - Fix `loki.source.journal` creation failing with an error when the journal file is not found. ([@&#8203;thampiotr](https://github.com/thampiotr)) - Fix graph UI so it generates correct URLs for components in `remotecfg` modules. ([@&#8203;patrickeasters](https://github.com/patrickeasters)) - Fix panic in `loki.write` when component is shutting down and `external_labels` are configured. ([@&#8203;kalleep](https://github.com/kalleep)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xMzAuMCIsInVwZGF0ZWRJblZlciI6IjQxLjEzMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
GregoryDosh deleted branch renovate/grafana-alloy-1.x 2025-10-01 03:25:15 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
action

Forgejo Action

  
automerge

   
dependencies

   
docker

   
pin-digest

   
skip-ci
No labels
action
automerge
dependencies
docker
pin-digest
skip-ci
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
homelab/ansible-collection!110
No description provided.