Menu
DocumentationGrafana CloudInstrument and send dataGrafana Agent
Grafana Cloud

Grafana Agent

Grafana Agent is an OpenTelemetry Collector distribution with configuration inspired by Terraform. It is designed to be flexible, performant, and compatible with multiple ecosystems such as Prometheus and OpenTelemetry.

Grafana Agent is based around components. Components are wired together to form programmable observability pipelines for telemetry collection, processing, and delivery.

Note

This page focuses mainly on Flow mode, the Terraform-inspired variant of Grafana Agent.

For information on other variants of Grafana Agent, refer to Introduction to Grafana Agent.

Grafana Agent can collect, transform, and send data to:

Why use Grafana Agent?

  • Vendor-neutral: Fully compatible with the Prometheus, OpenTelemetry, and Grafana open source ecosystems.
  • Every signal: Collect telemetry data for metrics, logs, traces, and continuous profiles.
  • Scalable: Deploy on any number of machines to collect millions of active series and terabytes of logs.
  • Battle-tested: Grafana Agent extends the existing battle-tested code from the Prometheus and OpenTelemetry Collector projects.
  • Powerful: Write programmable pipelines with ease, and debug them using a built-in UI.
  • Batteries included: Integrate with systems like MySQL, Kubernetes, and Apache to get telemetry that’s immediately useful.

Getting started

Supported platforms

  • Linux

    • Minimum version: kernel 2.6.32 or later
    • Architectures: AMD64, ARM64

  • Windows

    • Minimum version: Windows Server 2016 or later, or Windows 10 or later.
    • Architectures: AMD64

  • macOS

    • Minimum version: macOS 10.13 or later
    • Architectures: AMD64 (Intel), ARM64 (Apple Silicon)

  • FreeBSD

    • Minimum version: FreeBSD 10 or later
    • Architectures: AMD64

Release cadence

A new minor release is planned every six weeks for the entire Grafana Agent project, including Static mode, the Static mode Kubernetes operator, and Flow mode.

The release cadence is best-effort: releases may be moved forwards or backwards if needed. The planned release dates for future minor releases do not change if one minor release is moved.

Patch and security releases may be created at any time.