coredns/plugin/metrics
Miek Gieben c840caf1ef
Speed up testing (#4239)
* Speed up testing

* make notification run in the background, this recudes the test_readme
time from 18s to 0.10s
* reduce time for zone reload

* TestServeDNSConcurrent remove entirely. This took a whopping 58s for
  ... ? A few minutes staring didn't reveal wth it is actually testing.
  Making values smaller revealed race conditions in the tests. Remove
  entirely.

* Move many interval values to variables so we can reset them to short
  values for the tests.

* test_large_axfr: make the zone smaller. The number used 64K has no
  rational, make it 64/10 to speed up.
* TestProxyThreeWay: use client with shorter timeout

A few random tidbits in other tests.

Total time saved: 177s (almost 3m) - which makes it worthwhile again to
run the test locally:

this branch:

~~~
ok  	github.com/coredns/coredns/test	10.437s
cd plugin; time go t ./...
5,51s user 7,51s system 11,15s elapsed 744%CPU (
~~~

master:

~~~
ok  	github.com/coredns/coredns/test	35.252s
cd plugin; time go t ./...
157,64s user 15,39s system 50,05s elapsed 345%CPU ()
~~~
tests/ -25s
plugins/ -40s

This brings the total on 20s, and another 10s can be saved by fixing
dnstapio. Moving this to 5s would be even better, but 10s is also nice.

Signed-off-by: Miek Gieben <miek@miek.nl>

* Also 0.01

Signed-off-by: Miek Gieben <miek@miek.nl>
2020-10-30 10:27:04 +01:00
..
vars using promauto package to ensure all created metrics are properly registered (#4025) 2020-07-25 08:06:28 -07:00
context.go Remove server addr from the context (#2722) 2019-03-25 10:46:44 -07:00
handler.go Remove server addr from the context (#2722) 2019-03-25 10:46:44 -07:00
log_test.go Clean up tests logging (#1979) 2018-07-19 16:23:06 +01:00
metrics.go using promauto package to ensure all created metrics are properly registered (#4025) 2020-07-25 08:06:28 -07:00
metrics_test.go Speed up testing (#4239) 2020-10-30 10:27:04 +01:00
README.md Cleanup metrics (#3776) 2020-03-26 09:17:33 +01:00
registry.go plugin/metrcs: fix datarace on listeners (#2835) 2019-05-18 18:34:46 +01:00
setup.go For caddy v1 in our org (#4018) 2020-09-24 18:14:41 +02:00
setup_test.go For caddy v1 in our org (#4018) 2020-09-24 18:14:41 +02:00

prometheus

Name

prometheus - enables Prometheus metrics.

Description

With prometheus you export metrics from CoreDNS and any plugin that has them. The default location for the metrics is localhost:9153. The metrics path is fixed to /metrics. The following metrics are exported:

  • coredns_build_info{version, revision, goversion} - info about CoreDNS itself.
  • coredns_panics_total{} - total number of panics.
  • coredns_dns_requests_total{server, zone, proto, family, type} - total query count.
  • coredns_dns_request_duration_seconds{server, zone, type} - duration to process each query.
  • coredns_dns_request_size_bytes{server, zone, proto} - size of the request in bytes.
  • coredns_dns_do_requests_total{server, zone} - queries that have the DO bit set
  • coredns_dns_response_size_bytes{server, zone, proto} - response size in bytes.
  • coredns_dns_responses_total{server, zone, rcode} - response per zone and rcode.
  • coredns_plugin_enabled{server, zone, name} - indicates whether a plugin is enabled on per server and zone basis.

Each counter has a label zone which is the zonename used for the request/response.

Extra labels used are:

  • server is identifying the server responsible for the request. This is a string formatted as the server's listening address: <scheme>://[<bind>]:<port>. I.e. for a "normal" DNS server this is dns://:53. If you are using the bind plugin an IP address is included, e.g.: dns://127.0.0.53:53.
  • proto which holds the transport of the response ("udp" or "tcp")
  • The address family (family) of the transport (1 = IP (IP version 4), 2 = IP6 (IP version 6)).
  • type which holds the query type. It holds most common types (A, AAAA, MX, SOA, CNAME, PTR, TXT, NS, SRV, DS, DNSKEY, RRSIG, NSEC, NSEC3, IXFR, AXFR and ANY) and "other" which lumps together all other types.

If monitoring is enabled, queries that do not enter the plugin chain are exported under the fake name "dropped" (without a closing dot - this is never a valid domain name).

This plugin can only be used once per Server Block.

Syntax

prometheus [ADDRESS]

For each zone that you want to see metrics for.

It optionally takes a bind address to which the metrics are exported; the default listens on localhost:9153. The metrics path is fixed to /metrics.

Examples

Use an alternative listening address:

. {
    prometheus localhost:9253
}

Or via an environment variable (this is supported throughout the Corefile): export PORT=9253, and then:

. {
    prometheus localhost:{$PORT}
}

Bugs

When reloading, the Prometheus handler is stopped before the new server instance is started. If that new server fails to start, then the initial server instance is still available and DNS queries still served, but Prometheus handler stays down. Prometheus will not reply HTTP request until a successful reload or a complete restart of CoreDNS. Only the plugins that register as Handler are visible in coredns_plugin_enabled{server, zone, name}. As of today the plugins reload and bind will not be reported.