Skip to main content
Version: nightly

CoreDNS monitoring with Netdata

CoreDNS is a fast and flexible DNS server.

This module monitor one or more CoreDNS instances depending on configuration.

Metrics

All metrics have "coredns." prefix.

MetricScopeDimensionsUnits
dns_request_count_totalglobalrequestsrequests/s
dns_responses_count_totalglobalresponsesresponses/s
dns_request_count_total_per_statusglobalprocessed, droppedrequests/s
dns_no_matching_zone_dropped_totalglobaldroppedrequests/s
dns_panic_count_totalglobalpanicspanics/s
dns_requests_count_total_per_protoglobaludp, tcprequests/s
dns_requests_count_total_per_ip_familyglobalv4, v6requests/s
dns_requests_count_total_per_per_typeglobala, aaaa, mx, soa, cname, ptr, txt, ns, ds, dnskey, rrsig, nsec, nsec3, ixfr, any, otherrequests/s
dns_responses_count_total_per_rcodeglobalnoerror, formerr, servfail, nxdomain, notimp, refused, yxdomain, yxrrset, nxrrset, notauth, notzone, badsig, badkey, badtime, badmode, badname, badalg, badtrunc, badcookie, otherresponses/s
server_dns_request_count_totalserverrequestsrequests/s
server_dns_responses_count_totalserverresponsesresponses/s
server_dns_responses_count_totalserverresponsesresponses/s
server_request_count_total_per_statusserverprocessed, droppedrequests/s
server_requests_count_total_per_protoserverudp, tcprequests/s
server_requests_count_total_per_ip_familyserverv4, v6requests/s
server_requests_count_total_per_per_typeservera, aaaa, mx, soa, cname, ptr, txt, ns, ds, dnskey, rrsig, nsec, nsec3, ixfr, any, otherrequests/s
server_responses_count_total_per_rcodeservernoerror, formerr, servfail, nxdomain, notimp, refused, yxdomain, yxrrset, nxrrset, notauth, notzone, badsig, badkey, badtime, badmode, badname, badalg, badtrunc, badcookie, otherresponses/s
zone_dns_request_count_totalserverrequestsrequests/s
zone_dns_responses_count_totalserverresponsesresponses/s
zone_dns_responses_count_totalserverresponsesresponses/s
zone_requests_count_total_per_protoserverudp, tcprequests/s
zone_requests_count_total_per_ip_familyserverv4, v6requests/s
zone_requests_count_total_per_per_typeservera, aaaa, mx, soa, cname, ptr, txt, ns, ds, dnskey, rrsig, nsec, nsec3, ixfr, any, otherrequests/s
zone_responses_count_total_per_rcodeservernoerror, formerr, servfail, nxdomain, notimp, refused, yxdomain, yxrrset, nxrrset, notauth, notzone, badsig, badkey, badtime, badmode, badname, badalg, badtrunc, badcookie, otherresponses/s

Configuration

Edit the go.d/coredns.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/coredns.conf

The module needs only the url to a CoreDNS metrics-address. Here is an example for several instances:

jobs:
- name: local
url: http://127.0.0.1:9153/metrics

- name: remote
url: http://203.0.113.10:9153/metrics

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.

  • Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the plugins setting under [directories].

    cd /usr/libexec/netdata/plugins.d/
  • Switch to the netdata user.

    sudo -u netdata -s
  • Run the go.d.plugin to debug the collector:

    ./go.d.plugin -d -m coredns

Was this page helpful?

Contribute