Releases: grafana/alloy
v1.3.1
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.
v1.3.0
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 thebalancer_nameattribute has changed toround_robin
open-telemetry/opentelemetry-collector#10319
Breaking changes to non-GA functionality
-
Update Public preview
remotecfgargument frommetadatatoattributes. (@erikbaranowski) -
The default value of the argument
unmatchedin the blockroutesof the componentbeyla.ebpfwas changed fromunsettoheuristic(@marctc)
Features
-
Added community components support, enabling community members to implement and maintain components. (@wildum)
-
A new
otelcol.exporter.debugcomponent for printing OTel telemetry from
otherotelcolcomponents 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.
v1.3.0-rc.1
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 thebalancer_nameattribute has changed toround_robin
open-telemetry/opentelemetry-collector#10319
Breaking changes to non-GA functionality
-
Update Public preview
remotecfgargument frommetadatatoattributes. (@erikbaranowski) -
The default value of the argument
unmatchedin the blockroutesof the componentbeyla.ebpfwas changed fromunsettoheuristic(@marctc)
Features
-
Added community components support, enabling community members to implement and maintain components. (@wildum)
-
A new
otelcol.exporter.debugcomponent for printing OTel telemetry from
otherotelcolcomponents 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.
v1.3.0-rc.0
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 configureendpointusinglocalhostby default instead of0.0.0.0.
This may break the receiver in containerized environments like Kubernetes.
If you depend on0.0.0.0, configure theendpointattribute to explicitly use0.0.0.0.- [
otelcol.exporter.otlp,otelcol.exporter.loadbalancing]: Change the default gRPC load balancing strategy.
The default value for thebalancer_nameattribute has changed toround_robin
open-telemetry/opentelemetry-collector#10319
Breaking changes to non-GA functionality
-
Update Public preview
remotecfgargument frommetadatatoattributes. (@erikbaranowski) -
The default value of the argument
unmatchedin the blockroutesof the componentbeyla.ebpfwas changed fromunsettoheuristic(@marctc)
Features
-
Added community components support, enabling community members to implement and maintain components. (@wildum)
-
A new
otelcol.exporter.debugcomponent for printing OTel telemetry from
otherotelcolcomponents 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.
v1.2.1
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.
v1.2.0
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, andotelcol.receiver.jaegersettingmax_request_body_sizedefault changed from unlimited size to20MiB. This is due to CVE-2024-36129.
- Components
Breaking changes to non-GA functionality
- Component
otelcol.receiver.vcenterremovedvcenter.host.network.packet.errors,vcenter.host.network.packet.count, andvcenter.vm.network.packet.count.vcenter.host.network.packet.errorsreplaced byvcenter.host.network.packet.error.rate.vcenter.host.network.packet.countreplaced byvcenter.host.network.packet.rate.vcenter.vm.network.packet.countreplaced byvcenter.vm.network.packet.rate.
Features
-
Add an
otelcol.exporter.kafkacomponent to send OTLP metrics, logs, and traces to Kafka. -
Added
live debuggingto 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.deltatocumulativecomponent to convert metrics from
delta temporality to cumulative by accumulating samples in memory. (@rfratto) -
(Experimental) Add an
otelcol.receiver.datadogcomponent 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_protocolsoption toprometheus.scrape, which allows to control the preferred order of scrape protocols. (@thampiotr) -
Improved filesystem error handling when working with
loki.source.fileandlocal.file_match, which removes some false-positive error log messages on Windows (@thampiotr) -
Updates
receiver/vcenterto 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_decodeto standard library. (@mattdurham, @djcode) -
Add
base64_decodeto standard library. (@hainenber) -
Updated OpenTelemetry Contrib to v0.102.0. (@mattdurham)
-
otelcol.processor.resourcedetection: Added atagsconfig argument to theazuredetection mechanism. It exposes regex-matched Azure resource tags as OpenTelemetry resource attributes.
Bugfixes
-
Fixed an issue with
prometheus.scrapein 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.gitis given a revision that does not exist on the remote repo. (@hainenber) -
Fixed an issue with
loki.source.dockerwhere 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.
v1.2.0-rc.1
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):
Installation
Refer to our installation guide for how to install Grafana Alloy.
v1.2.0-rc.0
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, andotelcol.receiver.jaegersettingmax_request_body_sizedefault changed from unlimited size to20MiB. This is due to CVE-2024-36129.
- Components
Breaking changes to non-GA functionality
- Component
otelcol.receiver.vcenterremovedvcenter.host.network.packet.errors,vcenter.host.network.packet.count, andvcenter.vm.network.packet.count.vcenter.host.network.packet.errorsreplaced byvcenter.host.network.packet.error.rate.vcenter.host.network.packet.countreplaced byvcenter.host.network.packet.rate.vcenter.vm.network.packet.countreplaced byvcenter.vm.network.packet.rate.
Features
-
Add an
otelcol.exporter.kafkacomponent to send OTLP metrics, logs, and traces to Kafka. -
Added
live debuggingto 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.deltatocumulativecomponent to convert metrics from
delta temporality to cumulative by accumulating samples in memory. (@rfratto) -
(Experimental) Add an
otelcol.receiver.datadogcomponent 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_protocolsoption toprometheus.scrape, which allows to control the preferred order of scrape protocols. (@thampiotr) -
Improved filesystem error handling when working with
loki.source.fileandlocal.file_match, which removes some false-positive error log messages on Windows (@thampiotr) -
Updates
receiver/vcenterto 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_decodeto standard library. (@mattdurham, @djcode) -
Add
base64_decodeto standard library. (@hainenber) -
Updated OpenTelemetry Contrib to v0.102.0. (@mattdurham)
-
otelcol.processor.resourcedetection: Added atagsconfig argument to theazuredetection mechanism. It exposes regex-matched Azure resource tags as OpenTelemetry resource attributes.
Bugfixes
-
Fixed an issue with
prometheus.scrapein 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.gitis given a revision that does not exist on the remote repo. (@hainenber) -
Fixed an issue with
loki.source.dockerwhere 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.
v1.1.1
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
/inotelcomponent.MustNewType(ID).(@qclaogui) -
Exit Alloy immediately if the port it runs on is not available.
This port can be configured with--server.http.listen-addror using
the default listen address127.0.0.1:12345. (@mattdurham) -
Fix a panic in
loki.source.dockerwhen 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.snowflakewith the latest version of the exporter as of May 28, 2024 (@StefanKurek)- Fixes issue where returned
NULLvalues from database could cause unexpected errors.
- Fixes issue where returned
-
Bubble up SSH key conversion error to facilitate failed
import.git. (@hainenber)
Installation
Refer to our installation guide for how to install Grafana Alloy.
v1.1.0
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
-boringcryptosuffix and is only available on AMD64 and ARM64 Linux containers. (@rfratto, @mattdurham) -
(Public preview) Introduce
boringcryptorelease assets. BoringCrypto builds are publshed for Linux on AMD64 and ARM64 platforms. (@rfratto, @mattdurham) -
otelcol.exporter.loadbalancing: Add a newaws_cloud_mapresolver. (@ptodev) -
Introduce a
otelcol.receiver.file_statscomponent from the upstream OpenTelemetryfilestatsreceivercomponent. (@rfratto)
Enhancements
-
Update
prometheus.exporter.kafkawith 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 onmetadata_refresh_intervalinstead ofprune_interval_seconds. (@wildum) -
Don't restart tailers in
loki.source.kubernetescomponent 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 themimir.rules.kubernetescomponent to avoid conflicts when making calls to the Mimir API. (@56quarters)
Installation
Refer to our installation guide for how to install Grafana Alloy.