Skip to content

chore(deps): update alloy docker tag to v1.4.0

Tortoise caretaker requested to merge renovate/alloy-1.x into next

This MR contains the following updates:

Package Update Change
alloy minor v1.3.3 -> v1.4.0

Release Notes

grafana/alloy (alloy)

v1.4.0

Compare Source

Security fixes
Breaking changes

  • Some debug metrics for otelcol components have changed. (@​thampiotr) For example, otelcol.exporter.otlp's exporter_sent_spans_ratio_total metric is now otelcol_exporter_sent_spans_total.

  • [otelcol.processor.transform] The functions convert_sum_to_gauge and convert_gauge_to_sum must now be used in the metric context rather than in the datapoint context. https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34567 (@​wildum)

  • Upgrade Beyla from 1.7.0 to 1.8.2. A complete list of changes can be found on the Beyla releases page: https://github.com/grafana/beyla/releases. (@​wildum) It contains a few breaking changes for the component beyla.ebpf:

    • renamed metric process.cpu.state to cpu.mode
    • renamed metric beyla_build_info to beyla_internal_build_info
Features
  • Added Datadog Exporter community component, enabling exporting of otel-formatted Metrics and traces to Datadog. (@​polyrain)
  • (Experimental) Add an otelcol.processor.interval component to aggregate metrics and periodically forward the latest values to the next component in the pipeline.
  • (Experimental) Add a loki.secretfilter component to redact secrets from collected logs.
Enhancements

  • Clustering peer resolution through --cluster.join-addresses flag has been improved with more consistent behaviour, better error handling and added support for A/AAAA DNS records. If necessary, users can temporarily opt out of this new behaviour with the --cluster.use-discovery-v1, but this can only be used as a temporary measure, since this flag will be disabled in future releases. (@​thampiotr)

  • Added a new panel to Cluster Overview dashboard to show the number of peers seen by each instance in the cluster. This can help diagnose cluster split brain issues. (@​thampiotr)

  • Updated Snowflake exporter with performance improvements for larger environments. Also added a new panel to track deleted tables to the Snowflake mixin. (@​Caleb-Hurshman)

  • Add a otelcol.processor.groupbyattrs component to reassociate collected metrics that match specified attributes from opentelemetry. (@​kehindesalaam)

  • Update windows_exporter to v0.27.2. (@​jkroepke) The smb.enabled_list and smb_client.enabled_list doesn't have any effect anymore. All sub-collectors are enabled by default.

  • Live debugging of loki.process will now also print the timestamp of incoming and outgoing log lines. This is helpful for debugging stage.timestamp. (@​ptodev)

  • Add extra validation in beyla.ebpf to avoid panics when network feature is enabled. (@​marctc)

  • A new parameter aws_sdk_version_v2 is added for the cloudwatch exporters configuration. It enables the use of aws sdk v2 which has shown to have significant performance benefits. (@​kgeckhart, @​andriikushch)

  • prometheus.exporter.cloudwatch can now collect metrics from custom namespaces via the custom_namespace block. (@​ptodev)

  • Add the label alloy_cluster in the metric alloy_config_hash when the flag cluster.name is set to help differentiate between configs from the same alloy cluster or different alloy clusters. (@​wildum)

Bugfixes

  • Fix a bug where the scrape timeout for a Probe resource was not applied, overwriting the scrape interval instead. (@​morremeyer, @​stefanandres)

  • Fix a bug where custom components don't always get updated when the config is modified in an imported directory. (@​ante012)

  • Fixed an issue which caused loss of context data in Faro exception. (@​codecapitano)

  • Fixed an issue where providing multiple hostnames or IP addresses via --cluster.join-addresses would only use the first provided value. (@​thampiotr)

  • Fixed an issue where providing <hostname>:<port> in --cluster.join-addresses would only resolve with DNS to a single address, instead of using all the available records. (@​thampiotr)

  • Fixed an issue where clustering peers resolution via hostname in --cluster.join-addresses resolves to duplicated IP addresses when using SRV records. (@​thampiotr)

  • Fixed an issue where the connection_string for the loki.source.azure_event_hubs component was displayed in the UI in plaintext. (@​MorrisWitthein)

  • Fix a bug in discovery.* components where old targets would continue to be exported to downstream components. This would only happen if the config for discovery.* is reloaded in such a way that no new targets were discovered. (@​ptodev, @​thampiotr)

  • Fixed bug in loki.process with sampling stage where all components use same drop_counter_reason. (@​captncraig)

  • Fixed an issue (see https://github.com/grafana/alloy/issues/1599) where specifying both path and key in the remote.vault path configuration could result in incorrect URLs. The path and key arguments have been separated to allow for clear and accurate specification of Vault secrets. (@​PatMis16)

Other

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 MR becomes conflicted, or you tick the rebase/retry checkbox.

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

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

This MR has been generated by Renovate Bot. The local configuration can be found in the local Renovate Bot repository.

Merge request reports