Skip to main content

PowerDNS Authoritative Server monitoring with Netdata

PowerDNS Authoritative Server is a versatile nameserver which supports a large number of backends.

This module monitors one or more PowerDNS Authoritative Server instances, depending on your configuration.

It collects metrics from the internal webserver.

Used endpoints:


For collecting metrics via HTTP, we need:


  • Incoming questions in questions/s
  • Outgoing questions in questions/s
  • Cache Usage in events/s
  • Cache Size in entries
  • Latency in microseconds


Edit the go.d/powerdns.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/powerdns.conf

To add a new endpoint to collect metrics from, or change the URL that Netdata looks for, add or configure the name and url values. Endpoints can be both local or remote as long as they expose their metrics on the provided URL.

Here is an example with two endpoints:

- name: local
X-API-KEY: secret # static pre-shared authentication key for access to the REST API (api-key).
- name: remote
X-API-KEY: secret # static pre-shared authentication key for access to the REST API (api-key).

For all available options, see the PowerDNS Authoritative Server collector's configuration file.


To troubleshoot issues with the powerdns collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

First, navigate to your plugins directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch to the netdata user.

cd /usr/libexec/netdata/plugins.d/
sudo -u netdata -s

You can now run the go.d.plugin to debug the collector:

./go.d.plugin -d -m powerdns

Reach out

If you need help after reading this doc, search our community forum for an answer. There's a good chance someone else has already found a solution to the same issue.



Last updated on