prometheus.exporter.self
The prometheus.exporter.self
component collects and exposes metrics about Alloy itself.
Usage
prometheus.exporter.self "alloy" {
}
Arguments
prometheus.exporter.self
accepts no arguments.
Exported fields
The following fields are exported and can be referenced by other components.
Name | Type | Description |
---|---|---|
targets | list(map(string)) | The targets that can be used to collect exporter metrics. |
For example, the targets
can either be passed to a discovery.relabel
component to rewrite the targets’ label sets or to a prometheus.scrape
component that collects the exposed metrics.
The exported targets use the configured in-memory traffic address specified by the run command.
Component health
prometheus.exporter.self
is only reported as unhealthy if given
an invalid configuration.
Debug information
prometheus.exporter.self
doesn’t expose any component-specific
debug information.
Debug metrics
prometheus.exporter.self
doesn’t expose any component-specific
debug metrics.
Example
This example uses a prometheus.scrape
component to collect metrics
from prometheus.exporter.self
:
prometheus.exporter.self "example" {}
// Configure a prometheus.scrape component to collect Alloy metrics.
prometheus.scrape "demo" {
targets = prometheus.exporter.self.example.targets
forward_to = [prometheus.remote_write.demo.receiver]
}
prometheus.remote_write "demo" {
endpoint {
url = PROMETHEUS_REMOTE_WRITE_URL
basic_auth {
username = USERNAME
password = PASSWORD
}
}
}
Replace the following:
PROMETHEUS_REMOTE_WRITE_URL
: The URL of the Prometheus remote_write-compatible server to send metrics to.USERNAME
: The username to use for authentication to the remote_write API.PASSWORD
: The password to use for authentication to the remote_write API.
Compatible components
prometheus.exporter.self
has exports that can be consumed by the following components:
- Components that consume Targets
Note
Connecting some components may not be sensible or components may require further configuration to make the connection work correctly. Refer to the linked documentation for more details.