diff options
| author |  Miek Gieben <miek@miek.nl>
| 2018-04-20 15:03:59 +0100 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2018-04-20 15:03:59 +0100 |
| commit | ad13d88346d3e4686d92df20efb65af8f97dd7e1 (patch) | |
| tree | 407852424f64dbfe2d6241e1b2a4c73c87173119 | |
| parent | 8722336fff479e00900e3299f31063a9d1a76e9a (diff) | |
| download | coredns-ad13d88346d3e4686d92df20efb65af8f97dd7e1.tar.gz coredns-ad13d88346d3e4686d92df20efb65af8f97dd7e1.tar.zst coredns-ad13d88346d3e4686d92df20efb65af8f97dd7e1.zip | |
plugin/health: clarify server label (#1707)
Health overloaded metrics does not carry the server label. Explain why.
| -rw-r--r-- | plugin/health/README.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/plugin/health/README.md b/plugin/health/README.md index 35c4f18a2..f94355649 100644 --- a/plugin/health/README.md +++ b/plugin/health/README.md @@ -60,6 +60,9 @@ If monitoring is enabled (via the *prometheus* directive) then the following met be a local operation it should be fast. A (large) increases in this duration indicates the CoreDNS process is having trouble keeping up with its query load. +Note that this metric *does not* have a `server` label, because being overloaded is a symptom of +the running process, *not* a specific server. + ## Examples Run another health endpoint on http://localhost:8091. |