Monitor controller

Wed, 29 Jan 2025 11:00:55 +0000

How to monitor controller

The Grafana Agent Flow component controller exposes Prometheus metrics which you can use to investigate the controller state.

Metrics for the controller are exposed at the /metrics HTTP endpoint of the Grafana Agent Flow 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 Flow listens on for HTTP traffic.

The controller exposes the following metrics:

agent_component_controller_evaluating (Gauge): Set to 1 whenever the component controller is currently evaluating components. This value may be misrepresented depending on how fast evaluations complete or how often evaluations occur.
agent_component_controller_running_components (Gauge): The current number of running components by health. The health is represented in the health_type label.
agent_component_evaluation_seconds (Histogram): The time it takes to evaluate components after one of their dependencies is updated.
agent_component_dependencies_wait_seconds (Histogram): Time spent by components waiting to be evaluated after one of their dependencies is updated.
agent_component_evaluation_queue_size (Gauge): The current number of component evaluations waiting to be performed.

Monitor components

Wed, 29 Jan 2025 11:00:55 +0000

How to monitor components

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 Flow 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 Flow listens on for HTTP traffic.

Component-specific metrics 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 described the list of component-specific metrics that the component exposes. Not all components expose metrics.

Monitor Grafana Agent Flow on Grafana Labs

Monitor controller

How to monitor controller

Monitor components

How to monitor components