CoreDNS monitoring with Netdata
CoreDNS is a fast and flexible DNS server.
This module monitor one or more CoreDNS instances depending on configuration.
Charts#
It produces the following summary charts:
- Number Of DNS Requests in
requests/s - Number Of DNS Responses in
responses/s - Number Of Processed And Dropped DNS Requests in
requests/s - Number Of Dropped DNS Requests Because Of No Matching Zone in
requests/s - Number Of Panics in
panics/s - Number Of DNS Requests Per Transport Protocol in
requests/s - Number Of DNS Requests Per IP Family in
requests/s - Number Of DNS Requests Per Type in
requests/s - Number Of DNS Responses Per Rcode in
responses/s
Per server charts (if configured):
- Number Of DNS Requests in
requests/s - Number Of DNS Responses in
responses/s - Number Of Processed And Dropped DNS Requests in
requests/s - Number Of DNS Requests Per Transport Protocol in
requests/s - Number Of DNS Requests Per IP Family in
requests/s - Number Of DNS Requests Per Type in
requests/s - Number Of DNS Responses Per Rcode in
responses/s
Per zone charts (if configured):
- Number Of DNS Requests in
requests/s - Number Of DNS Responses in
responses/s - Number Of DNS Requests Per Transport Protocol in
requests/s - Number Of DNS Requests Per IP Family in
requests/s - Number Of DNS Requests Per Type in
requests/s - Number Of DNS Responses Per Rcode in
responses/s
Configuration#
Edit the go.d/coredns.conf configuration file using edit-config from the
Netdata config directory, which is typically at /etc/netdata.
The module needs only the url to a CoreDNS metrics-address. Here is an example for several instances:
For all available options, please see the module's configuration file.
Troubleshooting#
To troubleshoot issues with the coredns 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.
You can now run the go.d.plugin to debug the collector: