v1.5.1

This is release v1.5.1 of Grafana Alloy.

Upgrading

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

Notable changes:

Enhancements

• Logs from underlying clustering library memberlist are now surfaced with correct level (@thampiotr)

• Allow setting informer_sync_timeout in prometheus.operator.* components. (@captncraig)

• For sharding targets during clustering, loki.source.podlogs now only takes into account some labels. (@ptodev)

Bugfixes

• Fixed an issue in the pyroscope.write component to prevent TLS connection churn to Pyroscope when the pyroscope.receive_http clients don't request keepalive (@madaraszg-tulip)

• Fixed an issue in the pyroscope.write component with multiple endpoints not working correctly for forwarding profiles from pyroscope.receive_http (@madaraszg-tulip)

• Fixed a few race conditions that could lead to a deadlock when using import statements, which could lead to a memory leak on /metrics endpoint of an Alloy instance. (@thampiotr)

• Fix a race condition where the ui service was dependent on starting after the remotecfg service, which is not guaranteed. (@dehaansa & @erikbaranowski)

• Fixed an issue in the otelcol.exporter.prometheus component that would set series value incorrectly for stale metrics (@YusifAghalar)

• loki.source.podlogs: Fixed a bug which prevented clustering from working and caused duplicate logs to be sent.
  The bug only happened when no selector or namespace_selector blocks were specified in the Alloy configuration. (@ptodev)

• Fixed an issue in the pyroscope.write component to allow slashes in application names in the same way it is done in the Pyroscope push API (@marcsanmi)

• Fixed a crash when updating the configuration of remote.http. (@kinolaev)

• Fixed an issue in the otelcol.processor.attribute component where the actions delete and hash could not be used with the pattern argument. (@wildum)

• Fixed an issue in the prometheus.exporter.postgres component that would leak goroutines when the target was not reachable (@dehaansa)

Installation

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

v1.5.0

This is release v1.5.0 of Grafana Alloy.

Upgrading

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

Notable changes:

Breaking changes

• import.git: The default value for revision has changed from HEAD to main. (@ptodev)
  It is no longer allowed to set revision to "HEAD", "FETCH_HEAD", "ORIG_HEAD", "MERGE_HEAD", or "CHERRY_PICK_HEAD".

• The Otel update to v0.112.0 has a few breaking changes:

  • [otelcol.processor.deltatocumulative] Change max_streams default value to 9223372036854775807 (max int).
    open-telemetry/opentelemetry-collector-contrib#35048
  • [otelcol.connector.spanmetrics] Change namespace default value to traces.span.metrics.
    open-telemetry/opentelemetry-collector-contrib#34485
  • [otelcol.exporter.logging] Removed in favor of the otelcol.exporter.debug.
    open-telemetry/opentelemetry-collector#11337

Features

• Add the function path_join to the stdlib. (@wildum)

• Add pyroscope.receive_http component to receive and forward Pyroscope profiles (@marcsanmi)

• Add support to loki.source.syslog for the RFC3164 format ("BSD syslog"). (@sushain97)

• Add support to loki.source.api to be able to extract the tenant from the HTTP X-Scope-OrgID header (@QuentinBisson)

• (Experimental) Add a loki.secretfilter component to redact secrets from collected logs.

• (Experimental) Add a prometheus.write.queue component to add an alternative to prometheus.remote_write
  which allowing the writing of metrics to a prometheus endpoint. (@mattdurham)

• (Experimental) Add the arrary.combine_maps function to the stdlib. (@ptodev, @wildum)

• Add support bundle generation via the API endpoint /-/support (@dehaansa)

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

Installation

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

v1.5.0-rc.1

This is a release candidate v1.5.0-rc.1 of Grafana Alloy.

Upgrading

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

Notable changes:

Breaking changes

• import.git: The default value for revision has changed from HEAD to main. (@ptodev)
  It is no longer allowed to set revision to "HEAD", "FETCH_HEAD", "ORIG_HEAD", "MERGE_HEAD", or "CHERRY_PICK_HEAD".

• The Otel update to v0.112.0 has a few breaking changes:

  • [otelcol.processor.deltatocumulative] Change max_streams default value to 9223372036854775807 (max int).
    open-telemetry/opentelemetry-collector-contrib#35048
  • [otelcol.connector.spanmetrics] Change namespace default value to traces.span.metrics.
    open-telemetry/opentelemetry-collector-contrib#34485
  • [otelcol.exporter.logging] Removed in favor of the otelcol.exporter.debug.
    open-telemetry/opentelemetry-collector#11337

Features

• Add the function path_join to the stdlib. (@wildum)

• Add pyroscope.receive_http component to receive and forward Pyroscope profiles (@marcsanmi)

• Add support to loki.source.syslog for the RFC3164 format ("BSD syslog"). (@sushain97)

• Add support to loki.source.api to be able to extract the tenant from the HTTP X-Scope-OrgID header (@QuentinBisson)

• (Experimental) Add a loki.secretfilter component to redact secrets from collected logs.

• (Experimental) Add a prometheus.write.queue component to add an alternative to prometheus.remote_write
  which allowing the writing of metrics to a prometheus endpoint. (@mattdurham)

• (Experimental) Add the arrary.combine_maps function to the stdlib. (@ptodev, @wildum)

• Add support bundle generation via the API endpoint /-/support (@dehaansa)

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

Installation

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

v1.5.0-rc.0

This is a release candidate v1.5.0-rc.0 of Grafana Alloy.

Upgrading

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

Notable changes:

Breaking changes

• import.git: The default value for revision has changed from HEAD to main. (@ptodev)
  It is no longer allowed to set revision to "HEAD", "FETCH_HEAD", "ORIG_HEAD", "MERGE_HEAD", or "CHERRY_PICK_HEAD".

• The Otel update to v0.112.0 has a few breaking changes:

  • [otelcol.processor.deltatocumulative] Change max_streams default value to 9223372036854775807 (max int).
    open-telemetry/opentelemetry-collector-contrib#35048
  • [otelcol.connector.spanmetrics] Change namespace default value to traces.span.metrics.
    open-telemetry/opentelemetry-collector-contrib#34485
  • [otelcol.exporter.logging] Removed in favor of the otelcol.exporter.debug.
    open-telemetry/opentelemetry-collector#11337

Features

• Add the function path_join to the stdlib. (@wildum)

• Add pyroscope.receive_http component to receive and forward Pyroscope profiles (@marcsanmi)

• Add support to loki.source.syslog for the RFC3164 format ("BSD syslog"). (@sushain97)

• Add support to loki.source.api to be able to extract the tenant from the HTTP X-Scope-OrgID header (@QuentinBisson)

• (Experimental) Add a loki.secretfilter component to redact secrets from collected logs.

• (Experimental) Add a prometheus.write.queue component to add an alternative to prometheus.remote_write
  which allowing the writing of metrics to a prometheus endpoint. (@mattdurham)

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

Installation

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

v1.4.3

This is release v1.4.3 of Grafana Alloy.

Upgrading

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

Notable changes:

Bugfixes

• Fix an issue where some faro.receiver would drop multiple fields defined in payload.meta.browser, as fields were defined in the struct.

• pyroscope.scrape no longer tries to scrape endpoints which are not active targets anymore. (@wildum @mattdurham @dehaansa @ptodev)

• Fixed a bug with loki.source.podlogs not starting in large clusters due to short informer sync timeout. (@elburnetto-intapp)

• prometheus.exporter.windows: Fixed bug with exclude regular expression config arguments which caused missing metrics. (@ptodev)

Installation

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

v1.4.2

This is release v1.4.2 of Grafana Alloy.

Upgrading

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

Notable changes:

Bugfixes

• Update windows_exporter from v0.27.2 vo v0.27.3: (@jkroepke)

  • Fixes a bug where scraping Windows service crashes alloy

• Update yet-another-cloudwatch-exporter from v0.60.0 vo v0.61.0: (@morremeyer)

  • Fixes a bug where cloudwatch S3 metrics are reported as 0

• Issue 1687 - otelcol.exporter.awss3 fails to configure (@cydergoth)

  • Fix parsing of the Level configuration attribute in debug_metrics config block
  • Ensure "optional" debug_metrics config block really is optional

• Fixed an issue with loki.process where stage.luhn and stage.timestamp would not apply default configuration settings correctly (@thampiotr)

• Fixed an issue with loki.process where configuration could be reloaded even if there were no changes. (@ptodev, @thampiotr)

• Fix issue where loki.source.kubernetes took into account all labels, instead of specific logs labels. Resulting in duplication. (@mattdurham)

Installation

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

v1.4.1

This is release v1.4.1 of Grafana Alloy.

Upgrading

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

Notable changes:

Bugfixes

• Windows installer: Don't quote Alloy's binary path in the Windows Registry. (@jkroepke)

Installation

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

v1.3.4

This is release v1.3.4 of Grafana Alloy.

Upgrading

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

Notable changes:

Bugfixes

• Windows installer: Don't quote Alloy's binary path in the Windows Registry. (@jkroepke)

Installation

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

v1.4.0

This is release v1.4.0 of Grafana Alloy.

NOTE: If you are installing Alloy on Windows, use Alloy v1.4.1. Do not use v1.4.0 - it contains a broken Windows installer.

Upgrading

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

Notable changes:

Security fixes

• Add quotes to windows service path to prevent path interception attack. CVE-2024-8975 (@mattdurham)

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

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.

v1.3.3

This is release v1.3.3 of Grafana Alloy.

Upgrading

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

Notable changes:

Security fixes

• Add quotes to windows service path to prevent path interception attack. CVE-2024-8975 (@mattdurham)

Installation

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