Fix response_rcode_count_total metric (#3029)
This commit is contained in:
parent
2153cada45
commit
dae6aea292
2 changed files with 2 additions and 2 deletions
|
@ -98,7 +98,7 @@ If monitoring is enabled (via the *prometheus* directive) then the following met
|
|||
|
||||
* `coredns_forward_request_duration_seconds{to}` - duration per upstream interaction.
|
||||
* `coredns_forward_request_count_total{to}` - query count per upstream.
|
||||
* `coredns_forward_response_rcode_total{to, rcode}` - count of RCODEs per upstream.
|
||||
* `coredns_forward_response_rcode_count_total{to, rcode}` - count of RCODEs per upstream.
|
||||
* `coredns_forward_healthcheck_failure_count_total{to}` - number of failed health checks per upstream.
|
||||
* `coredns_forward_healthcheck_broken_count_total{}` - counter of when all upstreams are unhealthy,
|
||||
and we are randomly (this always uses the `random` policy) spraying to an upstream.
|
||||
|
|
|
@ -64,7 +64,7 @@ If monitoring is enabled (via the *prometheus* directive) then the following met
|
|||
|
||||
* `coredns_grpc_request_duration_seconds{to}` - duration per upstream interaction.
|
||||
* `coredns_grpc_request_count_total{to}` - query count per upstream.
|
||||
* `coredns_grpc_response_rcode_total{to, rcode}` - count of RCODEs per upstream.
|
||||
* `coredns_grpc_response_rcode_count_total{to, rcode}` - count of RCODEs per upstream.
|
||||
and we are randomly (this always uses the `random` policy) spraying to an upstream.
|
||||
|
||||
## Examples
|
||||
|
|
Loading…
Add table
Reference in a new issue