This is release v1.4.0-rc.2 of Grafana Alloy.

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

• [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.
  open-telemetry/opentelemetry-collector-contrib#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. (@ArthurSens)

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.

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 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)

Other

• Update OTel from v0.105.0 vo v0.108.0: (@wildum)

For a full list of changes, please refer to the CHANGELOG!

Installation

Refer to our installation guide for how to install Grafana Alloy.

This is release v1.3.1 of Grafana Alloy.

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Notable changes:

• Changed the cluster startup behaviour, reverting to the previous logic where a failure to resolve cluster join peers results in the node creating its own cluster. This is to facilitate the process of bootstrapping a new cluster following user feedback (@thampiotr)

• Fix a memory leak which would occur any time loki.process had its configuration reloaded. (@ptodev)

For a full list of changes, please refer to the CHANGELOG!

Installation

Refer to our installation guide for how to install Grafana Alloy.

This is release v1.3.0 of Grafana Alloy.

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

• [otelcol.exporter.otlp,otelcol.exporter.loadbalancing]: Change the default gRPC load balancing strategy.
  The default value for the balancer_name attribute has changed to round_robin
  open-telemetry/opentelemetry-collector#10319

Breaking changes to non-GA functionality

• Update Public preview remotecfg argument from metadata to attributes. (@erikbaranowski)

• The default value of the argument unmatched in the block routes of the component beyla.ebpf was changed from unset to heuristic (@marctc)

Features

• Added community components support, enabling community members to implement and maintain components. (@wildum)

• A new otelcol.exporter.debug component for printing OTel telemetry from
  other otelcol components to the console. (@BarunKGP)

For a full list of changes, please refer to the CHANGELOG!

Installation

Refer to our installation guide for how to install Grafana Alloy.

This is release v1.3.0-rc.1 of Grafana Alloy.

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

• [otelcol.exporter.otlp,otelcol.exporter.loadbalancing]: Change the default gRPC load balancing strategy.
  The default value for the balancer_name attribute has changed to round_robin
  open-telemetry/opentelemetry-collector#10319

Breaking changes to non-GA functionality

• Update Public preview remotecfg argument from metadata to attributes. (@erikbaranowski)

• The default value of the argument unmatched in the block routes of the component beyla.ebpf was changed from unset to heuristic (@marctc)

Features

• Added community components support, enabling community members to implement and maintain components. (@wildum)

• A new otelcol.exporter.debug component for printing OTel telemetry from
  other otelcol components to the console. (@BarunKGP)

For a full list of changes, please refer to the CHANGELOG!

Installation

Refer to our installation guide for how to install Grafana Alloy.

This is release v1.3.0-rc.0 of Grafana Alloy.

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

• otelcol.receiver.otlp, otelcol.receiver.jaeger, otelcol.extension.jaeger_remote_sampling, otelcol.receiver.zipkin
  will now configure endpoint using localhost by default instead of 0.0.0.0.
  This may break the receiver in containerized environments like Kubernetes.
  If you depend on 0.0.0.0, configure the endpoint attribute to explicitly use 0.0.0.0.
• [otelcol.exporter.otlp,otelcol.exporter.loadbalancing]: Change the default gRPC load balancing strategy.
  The default value for the balancer_name attribute has changed to round_robin
  open-telemetry/opentelemetry-collector#10319

Breaking changes to non-GA functionality

• Update Public preview remotecfg argument from metadata to attributes. (@erikbaranowski)

• The default value of the argument unmatched in the block routes of the component beyla.ebpf was changed from unset to heuristic (@marctc)

Features

• Added community components support, enabling community members to implement and maintain components. (@wildum)

• A new otelcol.exporter.debug component for printing OTel telemetry from
  other otelcol components to the console. (@BarunKGP)

For a full list of changes, please refer to the [CHANGELOG](https://github.com/grafana/alloy/blob/RELEASE_VERSION/CHANGELOG.md)!

Installation

Refer to our installation guide for how to install Grafana Alloy.

This is release v1.2.1 of Grafana Alloy.

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Notable changes:

For a full list of changes, please refer to the CHANGELOG!

Installation

Refer to our installation guide for how to install Grafana Alloy.

This is release v1.2.0 of Grafana Alloy.

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

• Updated OpenTelemetry to v0.102.1. (@mattdurham)
  • Components otelcol.receiver.otlp,otelcol.receiver.zipkin,otelcol.extension.jaeger_remote_sampling, and otelcol.receiver.jaeger setting max_request_body_size default changed from unlimited size to 20MiB. This is due to CVE-2024-36129.

Breaking changes to non-GA functionality

• Component otelcol.receiver.vcenter removed vcenter.host.network.packet.errors, vcenter.host.network.packet.count, and vcenter.vm.network.packet.count.
  • vcenter.host.network.packet.errors replaced by vcenter.host.network.packet.error.rate.
  • vcenter.host.network.packet.count replaced by vcenter.host.network.packet.rate.
  • vcenter.vm.network.packet.count replaced by vcenter.vm.network.packet.rate.

Features

• Add an otelcol.exporter.kafka component to send OTLP metrics, logs, and traces to Kafka.

• Added live debugging to the UI. Live debugging streams data as they flow through components for debugging telemetry data.
  Individual components must be updated to support live debugging. (@wildum)

• Added live debugging support for prometheus.relabel. (@wildum)

• (Experimental) Add a otelcol.processor.deltatocumulative component to convert metrics from
  delta temporality to cumulative by accumulating samples in memory. (@rfratto)

• (Experimental) Add an otelcol.receiver.datadog component to receive
  metrics and traces from Datadog. (@carrieedwards, @jesusvazquez, @alexgreenbank, @fedetorres93)

Enhancements

• (Public preview) Add native histogram support to otelcol.receiver.prometheus. (@wildum)

• Added scrape_protocols option to prometheus.scrape, which allows to control the preferred order of scrape protocols. (@thampiotr)

• Improved filesystem error handling when working with loki.source.file and local.file_match, which removes some false-positive error log messages on Windows (@thampiotr)

• Updates receiver/vcenter to use new features and bugfixes introduced in OTEL releases v0.100.0 and v0.101.0.
  Refer to the v0.100.0 and v0.101.0 release notes for more detailed information.

• Add yaml_decode to standard library. (@mattdurham, @djcode)

• Add base64_decode to standard library. (@hainenber)

• Updated OpenTelemetry Contrib to v0.102.0. (@mattdurham)

• otelcol.processor.resourcedetection: Added a tags config argument to the azure detection mechanism. It exposes regex-matched Azure resource tags as OpenTelemetry resource attributes.

Bugfixes

• Fixed an issue with prometheus.scrape in which targets that move from one cluster instance to another could have a staleness marker inserted and result in a gap in metrics (@thampiotr)

• Fix panic when import.git is given a revision that does not exist on the remote repo. (@hainenber)

• Fixed an issue with loki.source.docker where collecting logs from targets configured with multiple networks would result in errors. (@wildum)

For a full list of changes, please refer to the CHANGELOG!

Installation

Refer to our installation guide for how to install Grafana Alloy.

This is release v1.2.0-rc.1 of Grafana Alloy.

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Changes:

Security fixes

• Fixes the following vulnerabilities (@ptodev):
  • CVE-2024-35255
  • CVE-2024-36129

Installation

Refer to our installation guide for how to install Grafana Alloy.

This is release v1.2.0-rc.0 of Grafana Alloy.

Upgrading

Full a full list of changes, refer to the v1.2.0-rc.0 CHANGELOG.

Notable changes:

Breaking changes

• Updated OpenTelemetry to v0.102.1. (@mattdurham)
  • Components otelcol.receiver.otlp,otelcol.receiver.zipkin,otelcol.extension.jaeger_remote_sampling, and otelcol.receiver.jaeger setting max_request_body_size default changed from unlimited size to 20MiB. This is due to CVE-2024-36129.

Breaking changes to non-GA functionality

• Component otelcol.receiver.vcenter removed vcenter.host.network.packet.errors, vcenter.host.network.packet.count, and vcenter.vm.network.packet.count.
  • vcenter.host.network.packet.errors replaced by vcenter.host.network.packet.error.rate.
  • vcenter.host.network.packet.count replaced by vcenter.host.network.packet.rate.
  • vcenter.vm.network.packet.count replaced by vcenter.vm.network.packet.rate.

Features

• Add an otelcol.exporter.kafka component to send OTLP metrics, logs, and traces to Kafka.

• Added live debugging to the UI. Live debugging streams data as they flow through components for debugging telemetry data.
  Individual components must be updated to support live debugging. (@wildum)

• Added live debugging support for prometheus.relabel. (@wildum)

• (Experimental) Add a otelcol.processor.deltatocumulative component to convert metrics from
  delta temporality to cumulative by accumulating samples in memory. (@rfratto)

• (Experimental) Add an otelcol.receiver.datadog component to receive
  metrics and traces from Datadog. (@carrieedwards, @jesusvazquez, @alexgreenbank, @fedetorres93)

Enhancements

• (Public preview) Add native histogram support to otelcol.receiver.prometheus. (@wildum)

• Added scrape_protocols option to prometheus.scrape, which allows to control the preferred order of scrape protocols. (@thampiotr)

• Improved filesystem error handling when working with loki.source.file and local.file_match, which removes some false-positive error log messages on Windows (@thampiotr)

• Updates receiver/vcenter to use new features and bugfixes introduced in OTEL releases v0.100.0 and v0.101.0.
  Refer to the v0.100.0 and v0.101.0 release notes for more detailed information.

• Add yaml_decode to standard library. (@mattdurham, @djcode)

• Add base64_decode to standard library. (@hainenber)

• Updated OpenTelemetry Contrib to v0.102.0. (@mattdurham)

• otelcol.processor.resourcedetection: Added a tags config argument to the azure detection mechanism. It exposes regex-matched Azure resource tags as OpenTelemetry resource attributes.

Bugfixes

• Fixed an issue with prometheus.scrape in which targets that move from one cluster instance to another could have a staleness marker inserted and result in a gap in metrics (@thampiotr)

• Fix panic when import.git is given a revision that does not exist on the remote repo. (@hainenber)

• Fixed an issue with loki.source.docker where collecting logs from targets configured with multiple networks would result in errors. (@wildum)

Installation

Refer to our installation guide for how to install Grafana Alloy.

This is release v1.1.1 of Grafana Alloy.

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Notable changes:

• Fix panic when component ID contains / in otelcomponent.MustNewType(ID).(@qclaogui)

• Exit Alloy immediately if the port it runs on is not available.
  This port can be configured with --server.http.listen-addr or using
  the default listen address127.0.0.1:12345. (@mattdurham)

• Fix a panic in loki.source.docker when trying to stop a target that was never started. (@wildum)

• Fix error on boot when using IPv6 advertise addresses without explicitly
  specifying a port. (@matthewpi)

• Fix an issue where having long component labels (>63 chars) on otelcol.auth
  components lead to a panic. (@tpaschalis)

• Update prometheus.exporter.snowflake with the latest version of the exporter as of May 28, 2024 (@StefanKurek)

  • Fixes issue where returned NULL values from database could cause unexpected errors.

• Bubble up SSH key conversion error to facilitate failed import.git. (@hainenber)

Installation

Refer to our installation guide for how to install Grafana Alloy.