Releases: grafana/agent
v0.42.0
This is release v0.42.0
of Grafana Agent.
Upgrading
Read the relevant upgrade guides for specific instructions on upgrading from older versions:
Changes:
Security fixes
- Fixes following vulnerabilities (@ptodev)
Features
- A new
otelcol.exporter.debug
component for printing OTel telemetry from otherotelcol
components to the console. (@BarunKGP)
Bugfixes
-
Fix an issue which caused the config to be reloaded if a config reload was triggered but the config hasn't changed.
The bug only affected the "metrics" and "logs" subsystems in Static mode. (@ptodev) -
Fix a bug in Static mode and Flow which prevented config reloads to work if a Loki
metrics
stage is in the pipeline.
This resulted in a "failed to unregister all metrics from previous promtail" message. (@ptodev)
Enhancements
- Update to Go 1.22.5. (@ptodev)
Installation
Refer to our installation guides for how to install the variants of Grafana Agent:
v0.42.0-rc.0
This is release v0.42.0-rc.0
of Grafana Agent.
Upgrading
Read the relevant upgrade guides for specific instructions on upgrading from older versions:
Changes:
Security fixes
- Fixes following vulnerabilities (@ptodev)
Features
- A new
otelcol.exporter.debug
component for printing OTel telemetry from otherotelcol
components to the console. (@BarunKGP)
Bugfixes
-
Fix an issue which caused the config to be reloaded if a config reload was triggered but the config hasn't changed.
The bug only affected the "metrics" and "logs" subsystems in Static mode. (@ptodev) -
Fix a bug in Static mode and Flow which prevented config reloads to work if a Loki
metrics
stage is in the pipeline.
This resulted in a "failed to unregister all metrics from previous promtail" message. (@ptodev)
Enhancements
- Update to Go 1.22.5. (@ptodev)
Installation
Refer to our installation guides for how to install the variants of Grafana Agent:
v0.41.1
This is release v0.41.1
of Grafana Agent.
Upgrading
Read the relevant upgrade guides for specific instructions on upgrading from older versions:
Notable changes:
Breaking changes
- Applied OpenTelemetry CVE-2024-36129 fixes. (@mattdurham)
- Components
otelcol.receiver.otlp
,otelcol.receiver.zipkin
andotelcol.receiver.jaeger
settingmax_request_body_size
default changed from unlimited size to20MiB
.
- Components
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.41.0
This is release v0.41.0
of Grafana Agent.
Upgrading
Read the relevant upgrade guides for specific instructions on upgrading from older versions:
Notable changes:
Breaking changes
-
The default listen port for
otelcol.receiver.opencensus
has changed from
4317 to 55678 to align with upstream. (@rfratto) -
The default sync interval for
mimir.rules.kubernetes
has changed from30s
to5m
to reduce load on Mimir. (@56quarters)
Features
-
A new
loki.rules.kubernetes
component that discoversPrometheusRule
Kubernetes resources and loads them into a Loki Ruler instance. (@EStork09) -
A new
snmp_context
configuration argument forprometheus.exporter.snmp
and thesnmp
Static mode integration.
It overrides thecontext_name
parameter in the SNMP configuration file. (@ptodev)
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.5
This is release v0.40.5
of Grafana Agent.
Upgrading
Read the relevant upgrade guides for specific instructions on upgrading from older versions:
Notable changes:
Breaking changes
prometheus.exporter.postgres
has been updated to the latest upstream
version which changes the set of exported metrics. (@thampiotr)- The following metrics were removed:
pg_stat_database_session_time
,pg_stat_database_sessions
,
pg_stat_database_sessions_abandoned
,pg_stat_database_sessions_fatal
,
pg_stat_database_sessions_killed
,pg_stat_database_idle_in_transaction_time
,
pg_stat_database_checksum_failures
,pg_stat_database_checksum_last_failure
,
pg_stat_database_active_time
. - The following metrics were renamed:
pg_stat_bgwriter_buffers_alloc
,pg_stat_bgwriter_buffers_backend
,
pg_stat_bgwriter_buffers_backend_fsync
,pg_stat_bgwriter_buffers_checkpoint
,
pg_stat_bgwriter_buffers_clean
,pg_stat_bgwriter_checkpoint_sync_time
,
pg_stat_bgwriter_checkpoint_write_time
,pg_stat_bgwriter_checkpoints_req
,
pg_stat_bgwriter_checkpoints_timed
,pg_stat_bgwriter_maxwritten_clean
,
pg_stat_bgwriter_stats_reset
- the new names include the_total
suffix.
- The following metrics were removed:
Bugfixes
-
Fix an issue where the azure exporter was not correctly gathering subscription scoped metrics when only one region was configured (@kgeckhart)
-
Fixed an issue where creating a
prometheus.exporter.postgres
component with
multipledata_source_names
would result in an error. (@thampiotr) -
Fix a bug with the logs pipeline in static mode which prevented it from shutting down cleanly. (@ptodev)
Other changes
- Updating SNMP exporter from v0.24.1 to v0.26.0. (@ptodev)
Installation
Refer to our installation guides for how to install the variants of Grafana Agent:
v0.40.4
This is release v0.40.4
of Grafana Agent.
Upgrading
Read the relevant upgrade guides for specific instructions on upgrading from older versions:
Notable changes:
Security fixes
- Fixes following vulnerabilities (@ptodev)
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
onmetadata_refresh_interval
instead ofprune_interval_seconds
. (@wildum)
Bugfixes
- Update gcp_exporter to a newer version with a patch for incorrect delta histograms (@kgeckhart)
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.3
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
- Upgrade to Go 1.22.1 (@thampiotr)
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
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
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 anull
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
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 ofdisable_high_cardinality_metrics
totrue
. (@ptodev) -
Rename component
prometheus.exporter.agent
toprometheus.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 thedeclare
config block and import modules viaimport.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: