PowerDNS Recursor is a high-performance DNS recursor with built-in scripting capabilities.
The prerequisites for monitoring PowerDNS Recursor with Netdata are to have PowerDNS Recursor and Netdata installed on your system.
Netdata auto discovers hundreds of services, and for those it doesn’t turning on manual discovery is a one line configuration. For more information on configuring Netdata for PowerDNS Recursor monitoring please read the collector documentation.
You should now see the PowerDNS Recursor section on the Overview tab in Netdata Cloud already populated with charts about all the metrics you care about.
Netdata has a public demo space (no login required) where you can explore different monitoring use-cases and get a feel for Netdata.
Questions In is a metric that measures the number of incoming DNS requests from clients. It is a global metric that is measured in questions/s and consists of three dimensions: total, tcp, and ipv6. This metric is important to monitor because it helps to identify potential issues with the DNS server. If there are too many requests being sent to the DNS server, it can lead to issues such as timeouts or slow responses. By monitoring this metric, organizations can identify when the DNS server is becoming overloaded and can take steps to mitigate the issue before it becomes a problem.
Questions Out is a metric that measures the number of outgoing DNS requests from the DNS server. It is also a global metric that is measured in questions/s and consists of four dimensions: udp, tcp, ipv6, and throttled. This metric is important to monitor because it helps to identify potential issues with the DNS server that are related to outgoing requests. If the DNS server is sending out too many requests, it can lead to issues such as timeouts or slow responses. By monitoring this metric, organizations can identify when the DNS server is being overloaded and can take steps to mitigate the issue before it becomes a problem.
Answer Time is a metric that measures the time it takes for the DNS server to respond to requests. It is a global metric that consists of five dimensions: 0-1ms, 1-10ms, 10-100ms, 100-1000ms, and slow. This metric is important to monitor because it helps to identify potential issues with the DNS server that cause slow responses. If the DNS server is responding too slowly, it can lead to issues such as timeouts or poor performance. By monitoring this metric, organizations can identify when the DNS server is having performance issues and can take steps to mitigate the issue before it becomes a problem.
Timeouts is a metric that measures the number of requests that are timing out. It is a global metric that is measured in timeouts/s and consists of three dimensions: total, ipv4, and ipv6. This metric is important to monitor because it helps to identify potential issues with the DNS server that cause requests to time out. If the DNS server is timing out too many requests, it can lead to issues such as slow responses or poor performance. By monitoring this metric, organizations can identify when the DNS server is having performance issues and can take steps to mitigate the issue before it becomes a problem.
Drops is a metric that measures the number of requests that are dropped by the DNS server. It is a global metric that is measured in drops/s and consists of five dimensions: over-capacity-drops, query-pipe-full-drops, too-old-drops, truncated-drops, and empty-queries. This metric is important to monitor because it helps to identify potential issues with the DNS server that cause requests to be dropped. If the DNS server is dropping too many requests, it can lead to issues such as timeouts or slow responses. By monitoring this metric, organizations can identify when the DNS server is having performance issues and can take steps to mitigate the issue before it becomes a problem.
Cache Size is a metric that measures the size of the DNS server’s cache. It is a global metric that is measured in entries and consists of three dimensions: cache, packet-cache, and negative-cache. This metric is important to monitor because it helps to identify potential issues with the DNS server that cause the cache to become full. If the DNS server’s cache is full, it can lead to issues such as timeouts or slow responses. By monitoring this metric, organizations can identify when the DNS server is having performance issues and can take steps to mitigate the issue before it becomes a problem.