Grafana Alloy is the new name for our distribution of the OTel collector. Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to Grafana Alloy.

Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Open source

Component metrics

Grafana Agent Flow components may optionally expose Prometheus metrics which can be used to investigate the behavior of that component. These component-specific metrics are only generated when an instance of that component is running.

Component-specific metrics are different than any metrics being processed by the component. Component-specific metrics are used to expose the state of a component for observability, alerting, and debugging.

Component-specific metrics are exposed at the /metrics HTTP endpoint of the Grafana Agent HTTP server, which defaults to listening on http://localhost:12345.

The documentation for the [grafana-agent run][grafana-agent run] command describes how to modify the address Grafana Agent listens on for HTTP traffic.

Component-specific metrics will have a component_id label matching the component ID generating those metrics. For example, component-specific metrics for a prometheus.remote_write component labeled production will have a component_id label with the value prometheus.remote_write.production.

The reference documentation for each component will describe the list of component-specific metrics that component exposes. Not all components will expose metrics.