mirror of
https://github.com/coredns/coredns.git
synced 2025-11-18 18:02:16 -05:00
Fix forward metrics for backwards compatibility (#6178)
This commit is contained in:
@@ -115,20 +115,28 @@ plugin is also enabled:
|
||||
|
||||
If monitoring is enabled (via the *prometheus* plugin) then the following metric are exported:
|
||||
|
||||
* `coredns_forward_requests_total{to}` - query count per upstream.
|
||||
* `coredns_forward_responses_total{to}` - Counter of responses received per upstream.
|
||||
* `coredns_forward_request_duration_seconds{to, rcode, type}` - duration per upstream, RCODE, type
|
||||
* `coredns_forward_responses_total{to, rcode}` - count of RCODEs per upstream.
|
||||
* `coredns_forward_healthcheck_failures_total{to}` - number of failed health checks per upstream.
|
||||
* `coredns_forward_healthcheck_broken_total{}` - counter of when all upstreams are unhealthy,
|
||||
* `coredns_forward_healthcheck_broken_total{}` - count of when all upstreams are unhealthy,
|
||||
and we are randomly (this always uses the `random` policy) spraying to an upstream.
|
||||
* `coredns_forward_max_concurrent_rejects_total{}` - counter of the number of queries rejected because the
|
||||
* `coredns_forward_max_concurrent_rejects_total{}` - count of queries rejected because the
|
||||
number of concurrent queries were at maximum.
|
||||
* `coredns_forward_conn_cache_hits_total{to, proto}` - counter of connection cache hits per upstream and protocol.
|
||||
* `coredns_forward_conn_cache_misses_total{to, proto}` - counter of connection cache misses per upstream and protocol.
|
||||
* `coredns_proxy_request_duration_seconds{proxy_name="forward", to, rcode}` - histogram per upstream, RCODE
|
||||
* `coredns_proxy_healthcheck_failures_total{proxy_name="forward", to, rcode}`- count of failed health checks per upstream.
|
||||
* `coredns_proxy_conn_cache_hits_total{proxy_name="forward", to, proto}`- count of connection cache hits per upstream and protocol.
|
||||
* `coredns_proxy_conn_cache_misses_total{proxy_name="forward", to, proto}` - count of connection cache misses per upstream and protocol.
|
||||
|
||||
Where `to` is one of the upstream servers (**TO** from the config), `rcode` is the returned RCODE
|
||||
from the upstream, `proto` is the transport protocol like `udp`, `tcp`, `tcp-tls`.
|
||||
|
||||
The following metrics have recently been deprecated:
|
||||
* `coredns_forward_healthcheck_failures_total{to, rcode}`
|
||||
* Can be replaced with `coredns_proxy_healthcheck_failures_total{proxy_name="forward", to, rcode}`
|
||||
* `coredns_forward_requests_total{to}`
|
||||
* Can be replaced with `sum(coredns_proxy_request_duration_seconds_count{proxy_name="forward", to})`
|
||||
* `coredns_forward_responses_total{to, rcode}`
|
||||
* Can be replaced with `coredns_proxy_request_duration_seconds_count{proxy_name="forward", to, rcode}`
|
||||
* `coredns_forward_request_duration_seconds{to, rcode}`
|
||||
* Can be replaced with `coredns_proxy_request_duration_seconds{proxy_name="forward", to, rcode}`
|
||||
|
||||
## Examples
|
||||
|
||||
Proxy all requests within `example.org.` to a nameserver running on a different port:
|
||||
|
||||
Reference in New Issue
Block a user