v0.31.0

[ptodev]

This is release v0.31.0 of the Grafana Agent.

Upgrading

Read the upgrade guide for specific instructions on upgrading from older versions.

Notable changes:

Breaking changes

• Release binaries (including inside Docker containers) have been renamed to be
  prefixed with grafana- (@rfratto):

  • agent is now grafana-agent.
  • agentctl is now grafana-agentctl.
  • agent-operator is now grafana-agent-operator.

Deprecations

• A symbolic link in Docker containers from the old binary name to the new
  binary name has been added. These symbolic links will be removed in v0.33. (@rfratto)

Features

• New Grafana Agent Flow components:

  • loki.source.cloudflare reads logs from Cloudflare's Logpull API and
    forwards them to other loki components. (@tpaschalis)
  • loki.source.gcplog reads logs from GCP cloud resources using Pub/Sub
    subscriptions and forwards them to other loki components. (@tpaschalis)
  • loki.source.gelf listens for Graylog logs. (@mattdurham)
  • loki.source.heroku listens for Heroku messages over TCP a connection and
    forwards them to other loki components. (@erikbaranowski)
  • loki.source.journal read messages from systemd journal. (@mattdurham)
  • loki.source.kubernetes collects logs from Kubernetes pods using the
    Kubernetes API. (@rfratto)
  • loki.source.podlogs discovers PodLogs resources on Kubernetes and
    uses the Kubernetes API to collect logs from the pods specified by the
    PodLogs resource. (@rfratto)
  • loki.source.syslog listens for Syslog messages over TCP and UDP
    connections and forwards them to other loki components. (@tpaschalis)
  • loki.source.windowsevent reads logs from Windows Event Log. (@mattdurham)
  • otelcol.exporter.jaeger forwards OpenTelemetry data to a Jaeger server.
    (@erikbaranowski)
  • otelcol.exporter.loki forwards OTLP-formatted data to compatible loki
    receivers. (@tpaschalis)
  • otelcol.receiver.kafka receives telemetry data from Kafka. (@rfratto)
  • otelcol.receiver.loki receives Loki logs, converts them to the OTLP log
    format and forwards them to other otelcol components. (@tpaschalis)
  • otelcol.receiver.opencensus receives OpenConsensus-formatted traces or
    metrics. (@ptodev)
  • otelcol.receiver.zipkin receives Zipkin-formatted traces. (@rfratto)
  • phlare.scrape collects application performance profiles. (@cyriltovena)
  • phlare.write sends application performance profiles to Grafana Phlare.
    (@cyriltovena)
  • mimir.rules.kubernetes discovers PrometheusRule Kubernetes resources and
    loads them into a Mimir instance. (@Logiraptor)

• Flow components which work with relabeling rules (discovery.relabel,
  prometheus.relabel and loki.relabel) now export a new value named Rules.
  This value returns a copy of the currently configured rules. (@tpaschalis)

• New experimental feature: agent-management. Polls configured remote API to fetch new configs. (@spartan0x117)

• Introduce global configuration for logs. (@jcreixell)

Enhancements

• Handle faro-web-sdk View meta in app_agent_receiver. (@rlankfo)

• Grafana Agent Operator: add promtail limit stage to the operator. (@spartan0x117)

Bugfixes

• Flow UI: Fix the issue with messy layout on the component list page while browser window resize. (@xiyu95)

• Flow UI: Display the values of all attributes unless they are nil. (@ptodev)

• Flow: Fix issue where negative numbers would convert to floating-point values
  incorrectly, treating the sign flag as part of the number. (@rfratto)

• Flow: fix a goroutine leak when loki.source.file is passed more than one
  target with identical set of public labels. (@rfratto)

• Fix issue where removing and re-adding log instance configurations causes an
  error due to double registration of metrics (@spartan0x117, @jcreixell)

Other changes

• New windows containers for agent and agentctl. These can be found moving forward with the ${Version}-windows tags for grafana/agent and grafana/agentctl docker images (@erikbaranowski)

Installation:

Grafana Agent is currently distributed in plain binary form, Docker container images, a Windows installer, and a Kubernetes install script. Choose whichever fits your use-case best.

Kubernetes

Install directions here.

Docker container:

• https://hub.docker.com/r/grafana/agent

Docker containers are published as grafana/agent:v0.31.0. For Windows Docker containers, use grafana/agent:v0.31.0-windows instead.

Windows installer

The Windows installer is provided as a release asset for x64 machines.

Binary

We provide precompiled binary executables for the most common operating systems. Choose from the assets below for your matching operating system.

Note: ppc64le builds are currently considered secondary release targets and do not have the same level of support and testing as other platforms.

Example for the linux operating system on amd64:

# download the binary
curl -O -L "https://github.com/grafana/agent/releases/download/v0.31.0/grafana-agent-linux-amd64.zip"

# extract the binary
unzip "grafana-agent-linux-amd64.zip"

# make sure it is executable
chmod a+x "grafana-agent-linux-amd64"

agentctl

agentctl, a tool for helping you interact with the Agent, is available as a Docker image:

Docker containers are published as grafana/agentctl:v0.31.0. For Windows Docker containers, use grafana/agentctl:v0.31.0-windows instead.

Or as a binary. Like before, choose the assets below that matches your operating system. For example, with linux on amd64:

# download the binary
curl -O -L "https://github.com/grafana/agent/releases/download/v0.31.0/grafana-agentctl-linux-amd64.zip"

# extract the binary
unzip "grafana-agentctl-linux-amd64.zip"

# make sure it is executable
chmod a+x "grafana-agentctl-linux-amd64"

agent-operator

agent-operator, a Kubernetes Operator for the Grafana Agent, is available only as a Docker image:

docker pull "grafana/agent-operator:v0.31.0"

---

This discussion was created from the release v0.31.0.