aboutsummaryrefslogtreecommitdiff
path: root/man/coredns-reload.7
diff options
context:
space:
mode:
Diffstat (limited to 'man/coredns-reload.7')
-rw-r--r--man/coredns-reload.711
1 files changed, 8 insertions, 3 deletions
diff --git a/man/coredns-reload.7 b/man/coredns-reload.7
index c7cbfbfda..e9f1e9dae 100644
--- a/man/coredns-reload.7
+++ b/man/coredns-reload.7
@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
-.TH "COREDNS-RELOAD" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
+.TH "COREDNS-RELOAD" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -123,7 +123,7 @@ fail loading the new Corefile, abort and keep using the old process
.PP
After the aborted attempt to reload we are left with the old processes running, but the listener is
-closed in step 1; so the health endpoint is broken. The same can happen in the prometheus metrics plugin.
+closed in step 1; so the health endpoint is broken. The same can happen in the prometheus plugin.
.PP
In general be careful with assigning new port and expecting reload to work fully.
@@ -138,8 +138,13 @@ CoreDNS v1.7.0 and later does parse the Corefile and supports detecting changes
If monitoring is enabled (via the \fIprometheus\fP plugin) then the following metric is exported:
.IP \(bu 4
-\fB\fCcoredns_reload_failed_count_total{}\fR - counts the number of failed reload attempts.
+\fB\fCcoredns_reload_failed_total{}\fR - counts the number of failed reload attempts.
+.IP \(bu 4
+\fB\fCcoredns_reload_version_info{hash, value}\fR - record the hash value during reload.
+
+.PP
+Currently the type of \fB\fChash\fR is "md5", the \fB\fCvalue\fR is the returned hash value.
.SH "ALSO SEE"
.PP