github/coredns.io
4
0
Fork 0
mirror of https://github.com/coredns/coredns.io.git synced 2024-04-21 12:32:00 +00:00
Code Issues Releases Wiki Activity

auto content sync

Browse Source
This commit is contained in:
coredns-auto-sync[bot]
2020-03-26 08:18:51 +00:00
parent ce6b71f10d
commit 0fb5f69746
6 changed files with 25 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/plugins/acl.md
+3 -3
View File
@@ -4,7 +4,7 @@ description = "*acl* enforces access control policies on source ip and prevents
weight = 1
tags = ["plugin", "acl"]
categories = ["plugin"]
date = "2020-02-06T12:07:03.877382"
date = "2020-03-26T08:18:51.8775183"
+++
## Description
@@ -76,8 +76,8 @@ example.org {
If monitoring is enabled (via the _prometheus_ plugin) then the following metrics are exported:
- `coredns_request_block_count_total{server, zone}` - counter of DNS requests being blocked.
- `coredns_dns_blocked_requests_total{server, zone}` - counter of DNS requests being blocked.
- `coredns_request_allow_count_total{server}` - counter of DNS requests being allowed.
- `coredns_dns_allowed_requests_total{server}` - counter of DNS requests being allowed.
The `server` and `zone` labels are explained in the _metrics_ plugin documentation.
content/plugins/autopath.md
+2 -2
View File
@@ -4,7 +4,7 @@ description = "*autopath* allows for server-side search path completion."
weight = 4
tags = ["plugin", "autopath"]
categories = ["plugin"]
date = "2020-03-26T07:42:44.8774483"
date = "2020-03-26T08:18:51.8775183"
+++
## Description
@@ -34,7 +34,7 @@ If a plugin implements the `AutoPather` interface then it can be used.
If monitoring is enabled (via the *prometheus* plugin) then the following metric is exported:
* `coredns_autopath_success_count_total{server}` - counter of successfully autopath-ed queries.
* `coredns_autopath_success_total{server}` - counter of successfully autopath-ed queries.
The `server` label is explained in the *metrics* plugin documentation.
content/plugins/forward.md
+7 -7
View File
@@ -1,10 +1,10 @@
+++
title = "forward"
description = "*forward* facilitates proxying DNS messages to upstream resolvers."
weight = 19
weight = 20
tags = ["plugin", "forward"]
categories = ["plugin"]
date = "2020-03-06T10:54:38.8773883"
date = "2020-03-26T08:18:51.8775183"
+++
## Description
@@ -111,12 +111,12 @@ On each endpoint, the timeouts of the communication are set by default and autom
If monitoring is enabled (via the *prometheus* plugin) then the following metric are exported:
* `coredns_forward_request_duration_seconds{to}` - duration per upstream interaction.
* `coredns_forward_request_count_total{to}` - query count 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,
* `coredns_forward_requests_total{to}` - query count per upstream.
* `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,
and we are randomly (this always uses the `random` policy) spraying to an upstream.
* `max_concurrent_reject_count_total{}` - counter of the number of queries rejected because the
* `max_concurrent_rejects_total{}` - counter of the number of queries rejected because the
number of concurrent queries were at maximum.
Where `to` is one of the upstream servers (**TO** from the config), `rcode` is the returned RCODE
from the upstream.
content/plugins/grpc.md
+4 -4
View File
@@ -1,10 +1,10 @@
+++
title = "grpc"
description = "*grpc* facilitates proxying DNS messages to upstream resolvers via gRPC protocol."
weight = 20
weight = 21
tags = ["plugin", "grpc"]
categories = ["plugin"]
date = "2020-02-06T12:07:03.877382"
date = "2020-03-26T08:18:51.8775183"
+++
## Description
@@ -66,8 +66,8 @@ Also note the TLS config is "global" for the whole grpc proxy if you need a diff
If monitoring is enabled (via the *prometheus* plugin) then the following metric are exported:
* `coredns_grpc_request_duration_seconds{to}` - duration per upstream interaction.
* `coredns_grpc_request_count_total{to}` - query count per upstream.
* `coredns_grpc_response_rcode_count_total{to, rcode}` - count of RCODEs per upstream.
* `coredns_grpc_requests_total{to}` - query count per upstream.
* `coredns_grpc_responses_total{to, rcode}` - count of RCODEs per upstream.
and we are randomly (this always uses the `random` policy) spraying to an upstream.
## Examples
content/plugins/metrics.md
+6 -8
View File
@@ -1,10 +1,10 @@
+++
title = "prometheus"
description = "*prometheus* enables [Prometheus](https://prometheus.io/) metrics."
weight = 30
weight = 31
tags = ["plugin", "prometheus"]
categories = ["plugin"]
date = "2020-02-19T09:06:49.8774982"
date = "2020-03-26T08:18:51.8775183"
+++
## Description
@@ -14,14 +14,13 @@ The default location for the metrics is `localhost:9153`. The metrics path is fi
The following metrics are exported:
* `coredns_build_info{version, revision, goversion}` - info about CoreDNS itself.
* `coredns_panic_count_total{}` - total number of panics.
* `coredns_dns_request_count_total{server, zone, proto, family}` - total query count.
* `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_request_do_count_total{server, zone}` - queries that have the DO bit set
* `coredns_dns_request_type_count_total{server, zone, type}` - counter of queries per zone and type.
* `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_response_rcode_count_total{server, zone, rcode}` - response per zone and rcode.
* `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.
@@ -36,7 +35,6 @@ Extra labels used are:
* `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.
* The `response_rcode_count_total` has an extra label `rcode` which holds the rcode of the response.
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).
content/plugins/reload.md
+3 -3
View File
@@ -1,10 +1,10 @@
+++
title = "reload"
description = "*reload* allows automatic reload of a changed Corefile."
weight = 34
weight = 35
tags = ["plugin", "reload"]
categories = ["plugin"]
date = "2020-03-25T13:42:39.8773983"
date = "2020-03-26T08:18:51.8775183"
+++
## Description
@@ -101,7 +101,7 @@ CoreDNS v1.7.0 and later does parse the Corefile and supports detecting changes
If monitoring is enabled (via the *prometheus* plugin) then the following metric is exported:
* `coredns_reload_failed_count_total{}` - counts the number of failed reload attempts.
* `coredns_reload_failed_total{}` - counts the number of failed reload attempts.
* `coredns_reload_version_info{hash, value}` - record the hash value during reload.
Currently the type of `hash` is "md5", the `value` is the returned hash value.