This is documentation for the next version of Grafana Alloy Documentation. For the latest stable release, go to the latest version.

Documentationbreadcrumb arrow Grafana Alloybreadcrumb arrow Referencebreadcrumb arrow Componentsbreadcrumb arrow prometheusbreadcrumb arrow prometheus.exporter.dnsmasq
General availability (GA) Open source
Last reviewed: October 1, 2026

prometheus.exporter.dnsmasq

The prometheus.exporter.dnsmasq component embeds the dnsmasq_exporter to collect statistics from a dnsmasq server.

You can specify multiple prometheus.exporter.dnsmasq components by giving them different labels.

Usage

Alloy 
prometheus.exporter.dnsmasq "<LABEL>" {
}

Arguments

You can use the following arguments with prometheus.exporter.dnsmasq:

NameTypeDescriptionDefaultRequired
addressstringThe address of the dnsmasq server."localhost:53"no
expose_leasesboolExpose dnsmasq leases as metrics. Can cause high cardinality.falseno
leases_filestringThe path to the dnsmasq leases file."/var/lib/misc/dnsmasq.leases"no

The component sets the instance label on its exported targets to the value of address.

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.

NameTypeDescription
targetslist(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:

Alloy 
prometheus.exporter.dnsmasq "example" {
  address = "dnsmasq.example.com:53"
}

// Configure a prometheus.scrape component to collect dnsmasq 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 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.dnsmasq has exports that can be consumed by the following components:

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.