Make normalize return multiple "hosts" (= reverse zones) when a non-octet boundary cidr is given. Added pkg/cidr package that holds the cidr calculation routines; felt they didn't really fit dnsutil. This change means the IPNet return parameter isn't needed, the hosts are all correct. The tests that tests this is also removed: TestSplitHostPortReverse The fallout was that zoneAddr _also_ doesn't need the IPNet member, that in turn make it visible that zoneAddr in address.go duplicated a bunch of stuff from register.go; removed/refactored that too. Created a plugin.OriginsFromArgsOrServerBlock to help plugins do the right things, by consuming ZONE arguments; this now expands reverse zones correctly. This is mostly mechanical. Remove the reverse test in plugin/kubernetes which is a copy-paste from a core test (which has since been fixed). Remove MustNormalize as it has no plugin users. This change is not backwards compatible to plugins that have a ZONE argument that they parse in the setup util. All in-tree plugins have been updated. Signed-off-by: Miek Gieben <miek@miek.nl> |
||
---|---|---|
.. | ||
vars | ||
context.go | ||
handler.go | ||
log_test.go | ||
metrics.go | ||
metrics_test.go | ||
README.md | ||
registry.go | ||
setup.go | ||
setup_test.go |
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 setcoredns_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 isdns://: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.