• EnglishEspañol日本語한국어Português
  • Log inStart now

PowerDNS monitoring integration

Our PowerDNS integration collects and sends dimensional metrics from PowerDNS. You can view this metric data in pre-built dashboards, create alert policies, and create custom queries and charts.

Read on to install the integration, and to see what data we collect.

Compatibility and requirements

Our integration is compatible with PowerDNS Recursor and Authoritative Server.

Before installing the integration, make sure that you meet the following requirements:

To get data from PowerDNS infrastructure, our PowerDNS integration uses a third-party Prometheus exporter, which exposes Prometheus metrics on the port specified in the configuration. The integration collects these metrics, transforms them into entities, filters them, and then sends them to New Relic.

To enable the API, the webserver and the HTTP API need to be enabled.

Add these lines to the pdns.conf:


And restart, the following examples should start working:

curl -v -H 'X-API-Key: changeme' | jq .
curl -v -H 'X-API-Key: changeme'

For more information, Enabling Webserver and Api

Install and activate

To install the PowerDNS integration, choose your setup:

Did this doc help with your installation?

Configure the integration

To configure the integration, edit the config in the integration's YAML configuration file powerdns-config.yml.

Use the YAML configuration to place required login credentials and configure how your data is collected, depending on your setup and preference.

Since this integration is based on a prometheus exporter, settings applicable to other integrations, like interval, timeout or inventory_source are not supported.

PowerDNS instance settings

The following configuration options are available:





API URL of the powerdns service



Port to expose scrape endpoint on, If this is not provided a random port will be used to launch the exporter



Time until a scrape request times out



API key used to connect to the PowerDNS server


Example configurations

Find and use data

For more on how to find and use your data, see Understand integration data.

Metrics are attached to the Metric sample and event types of the entities POWERDNS_AUTHORITATIVE and POWERDNS_RECURSOR. You can query this data for troubleshooting purposes, or to create custom charts and dashboards.

Metric data


The following dimensional metrics are captured scraping the exporter and linked to the entity POWERDNS_AUTHORITATIVE:




powerdns_authoritative_uptime (count)

Uptime in seconds of the daemon.

  • type

powerdns_authoritative_packet_cache_size (gauge)

Number of entries in the packet cache.

powerdns_authoritative_recursive_queries_total (count)

Total number of recursive queries by status.

  • status

powerdns_authoritative_remote_queries (count)

Remote server IP addresses.

  • remote

powerdns_authoritative_security_status (gauge)

PDNS Server Security status based on security-status.secpoll.powerdns.com.

powerdns_authoritative_exceptions_total (count)

Total number of exceptions by error.

  • error

powerdns_authoritative_latency_average_seconds (gauge)

Average number of microseconds a packet spends within PowerDNS.

powerdns_authoritative_dnsupdate_queries_total (count)

Total number of DNS update queries by status.

  • status

powerdns_authoritative_qsize (gauge)

Number of packets waiting for database attention.

powerdns_authoritative_response_rcodes (count)

Distribution of rcodes.

  • rcode

powerdns_authoritative_signature_cache_size (gauge)

Number of entries in the signature cache.

powerdns_authoritative_queries_unauth (count)

Queries for domains that we are not authoritative for.

  • record

powerdns_authoritative_answers_bytes_total (count)

Total number of answer bytes sent over by protocol.

  • proto

powerdns_authoritative_queries (count)

UDP Queries Received.

  • record

powerdns_authoritative_exporter_json_parse_failures (count)

Number of errors while parsing PowerDNS JSON stats.

powerdns_authoritative_deferred_cache_actions (count)

Deferred cache actions because of maintenance by type.

  • type

powerdns_authoritative_up (gauge)

The last scrape of PowerDNS was successful.

powerdns_authoritative_query_cache_lookup (count)

Query cache lookups by result.

  • result

powerdns_authoritative_key_cache_size (gauge)

Number of entries in the key cache.

powerdns_authoritative_answers_total (count)

Total number of answers by protocol.

  • proto

powerdns_authoritative_packet_cache_lookup (count)

Packet cache lookups by result.

  • result

powerdns_authoritative_metadata_cache_size (gauge)

Number of entries in the metadata cache.

powerdns_authoritative_queries_total (count)

Total number of queries by protocol.

  • proto

powerdns_authoritative_cpu_utilisation (count)

Number of CPU milliseconds spent in user, and kernel space.

  • type

powerdns_authoritative_dnssec (count)

DNSSEC counters.

  • type

powerdns_authoritative_response_sizes (count)

Size distribution of responses.

  • size

powerdns_authoritative_exporter_total_scrapes (count)

Current total PowerDNS scrapes.

powerdns_authoritative_remote_queries_unauth (count)

Remote hosts querying domains for which we are not authoritative.

  • remote

The following dimensional metrics are captured scraping the exporter and linked to the entity POWERDNS_RECURSOR:




powerdns_recursor_incoming_queries_total (count)

Total number of incoming queries by network.

  • net

powerdns_recursor_outgoing_queries_total (count)

Total number of outgoing queries by network.

  • net

powerdns_recursor_cache_size (gauge)

Number of entries in the cache.

powerdns_recursor_cache_lookups_total (count)

Total number of cache lookups by result.

  • result

powerdns_recursor_exporter_json_parse_failures (count)

Number of errors while parsing PowerDNS JSON stats.

powerdns_recursor_answers_rcodes_total (count)

Total number of answers by response code.

  • rcode

powerdns_recursor_exporter_total_scrapes (count)

Current total PowerDNS scrapes.

powerdns_recursor_concurrent_queries (gauge)

Number of concurrent queries.

powerdns_recursor_answers_rtime_total (count)

Total number of answers grouped by response time slots.

  • timeslot

powerdns_recursor_latency_average_seconds (gauge)

Exponential moving average of question-to-answer latency.

powerdns_recursor_exceptions_total (count)

Total number of exceptions by error.

  • error

powerdns_recursor_response_time_seconds_sum (count)

Histogram of PowerDNS recursor response times in seconds. (sum metric)

powerdns_recursor_response_time_seconds_bucket (count)

Histogram of PowerDNS recursor response times in seconds. (bucket metric)

  • le

powerdns_recursor_up (gauge)

The last scrape of PowerDNS was successful.

Check the source code

This integration is open source software. This means you can browse its source code and send improvements, or create your own fork and build it.

Moreover this integration leverages an opensource exporter created by the community.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.