Skip to content

Releases: grafana/alloy

v1.1.0

14 May 22:59
v1.1.0
cf46a14
Compare
Choose a tag to compare

This is release v1.1.0 of Grafana Alloy.

Notable changes:

Full a full list of changes, refer to the v1.1.0 CHANGELOG.

Features

  • (Public preview) Add support for setting GOMEMLIMIT based on cgroup setting. (@mattdurham)

  • (Public preview) Introduce BoringCrypto Docker images. The BoringCrypto image is tagged with the -boringcrypto suffix and is only available on AMD64 and ARM64 Linux containers. (@rfratto, @mattdurham)

  • (Public preview) Introduce boringcrypto release assets. BoringCrypto builds are publshed for Linux on AMD64 and ARM64 platforms. (@rfratto, @mattdurham)

  • otelcol.exporter.loadbalancing: Add a new aws_cloud_map resolver. (@ptodev)

  • Introduce a otelcol.receiver.file_stats component from the upstream OpenTelemetry filestatsreceiver component. (@rfratto)

Enhancements

  • Update prometheus.exporter.kafka with the following functionalities (@wildum):

    • GSSAPI config
    • enable/disable PA_FX_FAST
    • set a TLS server name
    • show the offset/lag for all consumer group or only the connected ones
    • set the minimum number of topics to monitor
    • enable/disable auto-creation of requested topics if they don't already exist
    • regex to exclude topics / groups
    • added metric kafka_broker_info
  • In prometheus.exporter.kafka, the interpolation table used to compute estimated lag metrics is now pruned on metadata_refresh_interval instead of prune_interval_seconds. (@wildum)

  • Don't restart tailers in loki.source.kubernetes component by above-average time deltas if K8s version is >= 1.29.1 (@hainenber)

  • In mimir.rules.kubernetes, add support for running in a cluster of Alloy instances by electing a single instance as the leader for the mimir.rules.kubernetes component to avoid conflicts when making calls to the Mimir API. (@56quarters)

Installation

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

v1.1.0-rc.0

09 May 19:37
v1.1.0-rc.0
9200adf
Compare
Choose a tag to compare
v1.1.0-rc.0 Pre-release
Pre-release

This is pre-release v1.1.0-rc.0 of Grafana Alloy. Release v1.1.0 will be published after four working days on 2024-05-14 if no blocking issues are discovered with the release candidate.

Notable changes:

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

Features

  • (Public preview) Add support for setting GOMEMLIMIT based on cgroup setting. (@mattdurham)

  • (Public preview) Introduce BoringCrypto Docker images. The BoringCrypto image is tagged with the -boringcrypto suffix and
    is only available on AMD64 and ARM64 Linux containers. (@rfratto, @mattdurham)

  • (Public preview) Introduce boringcrypto release assets. BoringCrypto builds are publshed for Linux on AMD64 and ARM64 platforms. (@rfratto, @mattdurham)

  • otelcol.exporter.loadbalancing: Add a new aws_cloud_map resolver. (@ptodev)

  • Introduce a otelcol.receiver.file_stats component from the upstream OpenTelemetry filestatsreceiver component. (@rfratto)

Enhancements

  • Update prometheus.exporter.kafka with the following functionalities (@wildum):

    • GSSAPI config
    • enable/disable PA_FX_FAST
    • set a TLS server name
    • show the offset/lag for all consumer group or only the connected ones
    • set the minimum number of topics to monitor
    • enable/disable auto-creation of requested topics if they don't already exist
    • regex to exclude topics / groups
    • added metric kafka_broker_info
  • In prometheus.exporter.kafka, the interpolation table used to compute estimated lag metrics is now pruned on metadata_refresh_interval instead of prune_interval_seconds. (@wildum)

  • Don't restart tailers in loki.source.kubernetes component by above-average time deltas if K8s version is >= 1.29.1 (@hainenber)

  • In mimir.rules.kubernetes, add support for running in a cluster of Alloy instances by electing a single instance as the leader for the mimir.rules.kubernetes component to avoid conflicts when making calls to the Mimir API. (@56quarters)

Installation

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

v1.0.0

05 Apr 21:02
v1.0.0
1eef9b3
Compare
Choose a tag to compare

Grafana Labs is excited to announce Grafana Alloy, our open source distribution of the OpenTelemetry Collector. Alloy is a telemetry collector that is 100% OTLP compatible and offers native pipelines for OpenTelemetry and Prometheus telemetry formats, supporting metrics, logs, traces, and profiles.

We’ve built Alloy on the foundation of our work with Grafana Agent, while also incorporating lessons learned from some of the toughest use cases we’ve seen over the years. As a result, Alloy — which is production ready and released as v1.0 — is broadly compatible with the most popular open source telemetry signals. Plus, it includes enterprise-grade features — such as native clustering for production at scale and built-in Vault support for enhanced security — all out of the box.

Overall, Alloy is an extension of our “big tent” philosophy at Grafana Labs. We believe that organizations should own their observability strategy, choose their own tools, and have the freedom to bring all their data together in one view. Grafana Alloy helps you achieve just that as a telemetry collector that’s compatible with a suite of different signals that can meet a wide array of different needs.

Learn more: