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.

Documentation Grafana Alloy Troubleshoot Monitor components

Monitor components

Alloy 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 Alloy HTTP server, which defaults to listening on http://localhost:12345.

The documentation for the alloy run command describes how to modify the address Alloy 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.