This is documentation for the next version of Grafana Alloy Documentation. For the latest stable release, go to the latest version.
prometheus.exporter.dnsmasq
The prometheus.exporter.dnsmasq component embeds the dnsmasq_exporter for collecting statistics from a dnsmasq server.
Usage
prometheus.exporter.dnsmasq "<LABEL>" {
}Arguments
You can use the following arguments with prometheus.exporter.dnsmasq:
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
address | string | The address of the dnsmasq server. | "localhost:53" | no |
expose_leases | bool | Expose dnsmasq leases as metrics (high cardinality). | false | no |
leases_file | string | The path to the dnsmasq leases file. | "/var/lib/misc/dnsmasq.leases" | no |
Blocks
The prometheus.exporter.dnsmasq component doesn’t support any blocks. You can configure this component with 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.dnsmasq is only reported as unhealthy if given an invalid configuration.
In those cases, exported fields retain their last healthy values.
Debug information
prometheus.exporter.dnsmasq doesn’t expose any component-specific
debug information.
Debug metrics
prometheus.exporter.dnsmasq doesn’t expose any component-specific
debug metrics.
Example
The following example uses a prometheus.scrape component to collect metrics from prometheus.exporter.dnsmasq:
prometheus.exporter.dnsmasq "example" {
address = "localhost:53"
}
// Configure a prometheus.scrape component to collect github metrics.
prometheus.scrape "demo" {
targets = prometheus.exporter.dnsmasq.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 Prometheusremote_writecompatible server to send metrics to.<USERNAME>: The username to use for authentication to theremote_writeAPI.<PASSWORD>: The password to use for authentication to theremote_writeAPI.
Compatible components
prometheus.exporter.dnsmasq 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.



