Skip to content

Releases: grafana/agent

v0.40.3

14 Mar 16:31
b0f0bcd
Compare
Choose a tag to compare

This is release v0.40.3 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

Bugfixes

  • Fix a bug where structured metadata and parsed field are not passed further in loki.source.api (@marchellodev)

  • Change import.git to use Git pulls rather than fetches to fix scenarios where the local code did not get updated. (@mattdurham)

Other changes

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

Installation

Refer to our installation guides for how to install the variants of Grafana Agent:

v0.40.2

05 Mar 21:20
v0.40.2
caf49e8
Compare
Choose a tag to compare

This is release v0.40.2 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

Bugfixes

  • Set permissions on the Grafana Agent [Flow] folder when installing via the windows installer rather than relying on the parent folder permissions. (@erikbaranowski)
  • Set restricted viewing permissions on the agent-config.yaml (static mode) or config.river (flow mode) when installing via the Windows installer if the configuration file does not already exist. (@erikbaranowski)
  • Fix an issue where the import config node would not run after a config reload. (@wildum)
  • Fix an issue where Loki could reject a batch of logs when structured metadata feature is used. (@thampiotr)
  • Fix a duplicate metrics registration panic when recreating static mode metric instance's write handler. (@rfratto, @hainenber)

Other changes

  • Change the Docker base image for Linux containers to public.ecr.aws/ubuntu/ubuntu:mantic. (@hainenber)

Installation

Refer to our installation guides for how to install the variants of Grafana Agent:

v0.40.1

29 Feb 19:58
v0.40.1
f222e2e
Compare
Choose a tag to compare

This is release v0.40.1 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

  • Fix an issue where the logging config block would trigger an error when trying to send logs to components that were not running. (@wildum)
  • Fix an issue where a custom component might be wired to a local declare instead of an import declare when they have the same label. (@wildum)
  • Fix an issue where flow mode panics if the logging config block is given a null Loki receiver to write log entries to. (@rfratto)

Installation

Refer to our installation guides for how to install the variants of Grafana Agent:

v0.40.0

27 Feb 11:41
v0.40.0
9be9693
Compare
Choose a tag to compare

This is release v0.40.0 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

  • Prohibit the configuration of services within modules. (@wildum)

  • For otelcol.exporter components, change the default value of disable_high_cardinality_metrics to true. (@ptodev)

  • Rename component prometheus.exporter.agent to prometheus.exporter.self to clear up ambiguity. (@hainenber)

Deprecations

  • Module components have been deprecated in favor of import and declare configuration blocks. These deprecated components will be removed in the next release. (@wildum)

Features

  • Modules have been redesigned to split the import logic from the instantiation.
    You can now define custom components via the declare config block and import modules via import.git, import.http, import.string, import.file. (@wildum)

  • A new discovery.process component for discovering Linux OS processes on the current host. (@korniltsev)

  • A new pyroscope.java component for profiling Java processes using async-profiler. (@korniltsev)

  • A new otelcol.processor.resourcedetection component which inserts resource attributes
    to OTLP telemetry based on the host on which Grafana Agent is running. (@ptodev)

  • Expose track_timestamps_staleness on Prometheus scraping, to fix the issue where container metrics live for 5 minutes after the container disappears. (@ptodev)

  • Introduce the remotecfg service that enables loading configuration from a
    remote endpoint. (@tpaschalis)

  • Add otelcol.connector.host_info component to gather usage metrics for cloud users. (@rlankfo, @jcreixell)

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

Installation

Refer to our installation guides for how to install the variants of Grafana Agent:

v0.40.0-rc.2

26 Feb 11:25
v0.40.0-rc.2
29e380e
Compare
Choose a tag to compare
v0.40.0-rc.2 Pre-release
Pre-release

This is release v0.40.0-rc.2 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

  • Prohibit the configuration of services within modules. (@wildum)

  • For otelcol.exporter components, change the default value of disable_high_cardinality_metrics to true. (@ptodev)

  • Rename component prometheus.exporter.agent to prometheus.exporter.self to clear up ambiguity. (@hainenber)

Deprecations

  • Module components have been deprecated in favor of import and declare configuration blocks. These deprecated components will be removed in the next release. (@wildum)

Features

  • Modules have been redesigned to split the import logic from the instantiation.
    You can now define custom components via the declare config block and import modules via import.git, import.http, import.string, import.file. (@wildum)

  • A new discovery.process component for discovering Linux OS processes on the current host. (@korniltsev)

  • A new pyroscope.java component for profiling Java processes using async-profiler. (@korniltsev)

  • A new otelcol.processor.resourcedetection component which inserts resource attributes
    to OTLP telemetry based on the host on which Grafana Agent is running. (@ptodev)

  • Expose track_timestamps_staleness on Prometheus scraping, to fix the issue where container metrics live for 5 minutes after the container disappears. (@ptodev)

  • Introduce the remotecfg service that enables loading configuration from a
    remote endpoint. (@tpaschalis)

  • Add otelcol.connector.host_info component to gather usage metrics for cloud users. (@rlankfo, @jcreixell)

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

Installation

Refer to our installation guides for how to install the variants of Grafana Agent:

v0.40.0-rc.1

23 Feb 14:43
v0.40.0-rc.1
299d17b
Compare
Choose a tag to compare
v0.40.0-rc.1 Pre-release
Pre-release

This is release v0.40.0-rc.1 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

  • Prohibit the configuration of services within modules. (@wildum)

  • For otelcol.exporter components, change the default value of disable_high_cardinality_metrics to true. (@ptodev)

  • Rename component prometheus.exporter.agent to prometheus.exporter.self to clear up ambiguity. (@hainenber)

Deprecations

  • Module components have been deprecated in favor of import and declare configuration blocks. These deprecated components will be removed in the next release. (@wildum)

Features

  • Modules have been redesigned to split the import logic from the instantiation.
    You can now define custom components via the declare config block and import modules via import.git, import.http, import.string, import.file. (@wildum)

  • A new discovery.process component for discovering Linux OS processes on the current host. (@korniltsev)

  • A new pyroscope.java component for profiling Java processes using async-profiler. (@korniltsev)

  • A new otelcol.processor.resourcedetection component which inserts resource attributes
    to OTLP telemetry based on the host on which Grafana Agent is running. (@ptodev)

  • Expose track_timestamps_staleness on Prometheus scraping, to fix the issue where container metrics live for 5 minutes after the container disappears. (@ptodev)

  • Introduce the remotecfg service that enables loading configuration from a
    remote endpoint. (@tpaschalis)

  • Add otelcol.connector.host_info component to gather usage metrics for cloud users. (@rlankfo, @jcreixell)

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

Installation

Refer to our installation guides for how to install the variants of Grafana Agent:

v0.40.0-rc.0

22 Feb 14:58
v0.40.0-rc.0
aeeb9d6
Compare
Choose a tag to compare
v0.40.0-rc.0 Pre-release
Pre-release

This is release v0.40.0-rc.0 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

  • Prohibit the configuration of services within modules. (@wildum)

  • For otelcol.exporter components, change the default value of disable_high_cardinality_metrics to true. (@ptodev)

  • Rename component prometheus.exporter.agent to prometheus.exporter.self to clear up ambiguity. (@hainenber)

Deprecations

  • Module components have been deprecated in favor of import and declare configuration blocks. These deprecated components will be removed in the next release. (@wildum)

Features

  • Modules have been redesigned to split the import logic from the instantiation.
    You can now define custom components via the declare config block and import modules via import.git, import.http, import.string, import.file. (@wildum)

  • A new discovery.process component for discovering Linux OS processes on the current host. (@korniltsev)

  • A new pyroscope.java component for profiling Java processes using async-profiler. (@korniltsev)

  • A new otelcol.processor.resourcedetection component which inserts resource attributes
    to OTLP telemetry based on the host on which Grafana Agent is running. (@ptodev)

  • Expose track_timestamps_staleness on Prometheus scraping, to fix the issue where container metrics live for 5 minutes after the container disappears. (@ptodev)

  • Introduce the remotecfg service that enables loading configuration from a
    remote endpoint. (@tpaschalis)

  • Add otelcol.connector.host_info component to gather usage metrics for cloud users. (@rlankfo, @jcreixell)

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

Installation

Refer to our installation guides for how to install the variants of Grafana Agent:

v0.39.2

31 Jan 17:00
v0.39.2
deae3f8
Compare
Choose a tag to compare

This is release v0.39.2 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

Bugfixes

  • Fix error introduced in v0.39.0 preventing remote write to Amazon Managed Prometheus. (@captncraig)

  • An error will be returned in the converter from Static to Flow when scrape_integration is set
    to true but no remote_write is defined. (@erikbaranowski)

Installation

Refer to our installation guides for how to install the variants of Grafana Agent:

v0.39.1

19 Jan 13:04
v0.39.1
7dbb39c
Compare
Choose a tag to compare

This is release v0.39.1 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

Security fixes

Bugfixes

  • Fix issue where installing the Windows Agent Flow installer would hang then crash. (@mattdurham)

Installation

Refer to our installation guides for how to install the variants of Grafana Agent:

v0.39.0

09 Jan 16:35
v0.39.0
402672c
Compare
Choose a tag to compare

This is release v0.39.0 of Grafana Agent.

Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

Notable changes:

Breaking changes

  • otelcol.receiver.prometheus will drop all otel_scope_info metrics when converting them to OTLP. (@wildum)

    • If the otel_scope_info metric has labels otel_scope_name and otel_scope_version,
      their values will be used to set OTLP Instrumentation Scope name and version respectively.
    • Labels of otel_scope_info metrics other than otel_scope_name and otel_scope_version
      are added as scope attributes with the matching name and version.
  • The target block in prometheus.exporter.blackbox requires a mandatory name
    argument instead of a block label. (@hainenber)

  • In the azure exporter, dimension options will no longer be validated by the Azure API. (@kgeckhart)

    • This change will not break any existing configurations and you can opt in to validation via the validate_dimensions configuration option.
    • Before this change, pulling metrics for azure resources with variable dimensions required one configuration per metric + dimension combination to avoid an error.
    • After this change, you can include all metrics and dimensions in a single configuration and the Azure APIs will only return dimensions which are valid for the various metrics.

Features

  • A new discovery.ovhcloud component for discovering scrape targets on OVHcloud. (@ptodev)
  • Allow specifying additional containers to run. (@juangom)

Enhancements

  • Flow Windows service: Support environment variables. (@jkroepke)

  • Allow disabling collection of root Cgroup stats in
    prometheus.exporter.cadvisor (flow mode) and the cadvisor integration
    (static mode). (@hainenber)

  • Grafana Agent on Windows now automatically restarts on failure. (@hainenber)

  • Added metrics, alerts and dashboard visualisations to help diagnose issues
    with unhealthy components and components that take too long to evaluate. (@thampiotr)

  • The http config block may now reference exports from any component.
    Previously, only remote.* and local.* components could be referenced
    without a circular dependency. (@rfratto)

  • Add support for Basic Auth-secured connection with Elasticsearch cluster using prometheus.exporter.elasticsearch. (@hainenber)

  • Add a resource_to_telemetry_conversion argument to otelcol.exporter.prometheus
    for converting resource attributes to Prometheus labels. (@hainenber)

  • pyroscope.ebpf support python on arm64 platforms. (@korniltsev)

  • otelcol.receiver.prometheus does not drop histograms without buckets anymore. (@wildum)

  • Added exemplars support to otelcol.receiver.prometheus. (@wildum)

  • mimir.rules.kubernetes may now retry its startup on failure. (@hainenber)

  • Added links between compatible components in the documentation to make it
    easier to discover them. (@thampiotr)

  • Allow defining HTTPClientConfig for discovery.ec2. (@cmbrad)

  • The remote.http component can optionally define a request body. (@tpaschalis)

  • Added support for loki.write to flush WAL on agent shutdown. (@thepalbi)

  • Add support for integrations-next static to flow config conversion. (@erikbaranowski)

  • Add support for passing extra arguments to the static converter such as -config.expand-env. (@erikbaranowski)

  • Added 'country' mmdb-type to log pipeline-stage geoip. (@superstes)

  • Azure exporter enhancements for flow and static mode, (@kgeckhart)

    • Allows for pulling metrics at the Azure subscription level instead of resource by resource
    • Disable dimension validation by default to reduce the number of exporter instances needed for full dimension coverage
  • Add max_cache_size to prometheus.relabel to allow configurability instead of hard coded 100,000. (@mattdurham)

  • Add support for http_sd_config within a scrape_config for prometheus to flow config conversion. (@erikbaranowski)

  • discovery.lightsail now supports additional parameters for configuring HTTP client settings. (@ptodev)

  • Add sample_age_limit to remote_write config to drop samples older than a specified duration. (@marctc)

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

Installation

Refer to our installation guides for how to install the variants of Grafana Agent: