TrueCloudLab/coredns
16
0
Fork 2
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions
coredns/middleware/prometheus
History
Miek Gieben 7e05aa8069 Enable monitoring for non middleware 
If monitoring is enabled for one zone, also enable it for when the

server reports REFUSED. Normally the metrics are only enabled if

you enter the middleware, with this you'll see REFUSED queries.

Each of these are reported agains the root zone otherwise
2016-04-06 14:13:29 +01:00
..
handler.go Enable monitoring for non middleware 2016-04-06 14:13:29 +01:00
metrics.go Some monitoring refactoring 2016-04-06 13:42:56 +01:00
README.md A health middleware 2016-04-06 09:21:46 +01:00

README.md

prometheus

This module enables prometheus metrics for CoreDNS.

The following metrics are exported:

  • coredns_dns_request_count_total
  • coredns_dns_request_duration_seconds
  • coredns_dns_response_size_bytes
  • coredns_dns_response_rcode_count_total

Each counter has a label zone which is the zonename used for the request/response, and a label qtype which old the query type. The response_rcode_count_total has an extra label rcode which holds the rcode of the response.

Restarting CoreDNS will stop the monitoring. This is a bug. Also this upstream Caddy bug.

Syntax

prometheus

For each zone that you want to see metrics for.

It optionally takes an address where the metrics are exported, the default is localhost:9135. The metrics path is fixed to /metrics.

Examples