PowerDNS Recursor is a high-performance DNS recursor with built-in scripting
This module monitors one or more
PowerDNS Recursor instances, depending on your configuration.
It collects metrics from the internal webserver.
For collecting metrics via HTTP, we need:
- Incoming questions in
- Outgoing questions in
- Queries answered within a time range in
- Timeouts on outgoing UDP queries in
- Drops in
- Cache Usage in
- Cache Size in
go.d/powerdns_recursor.conf configuration file using
edit-config from the
Netdata config directory, which is typically at
To add a new endpoint to collect metrics from, or change the URL that Netdata looks for, add or configure the
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:
For all available options, see the PowerDNS Recursor collector's configuration file.
To troubleshoot issues with the
powerdns_recursor 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
netdata.conf and look for the setting
plugins directory. Once you're in the plugin's directory, switch
You can now run the
go.d.plugin to debug the collector: