From 5cd8472384eb028b56a927d90cecf097c9be45e9 Mon Sep 17 00:00:00 2001 From: Chris O'Haver Date: Thu, 26 Mar 2020 10:24:56 -0400 Subject: [PATCH] Fix plugin name in project README (#3683) * Update README.md Signed-off-by: Chris O'Haver * fix readme occurances Signed-off-by: Chris O'Haver --- README.md | 2 +- plugin/cache/README.md | 2 +- plugin/reload/README.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 10dc9f2ba..ce070fba8 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ Currently CoreDNS is able to: * Use etcd as a backend (replacing [SkyDNS](https://github.com/skynetservices/skydns)) (*etcd*). * Use k8s (kubernetes) as a backend (*kubernetes*). * Serve as a proxy to forward queries to some other (recursive) nameserver (*forward*). -* Provide metrics (by using Prometheus) (*metrics*). +* Provide metrics (by using Prometheus) (*prometheus*). * Provide query (*log*) and error (*errors*) logging. * Integrate with cloud providers (*route53*). * Support the CH class: `version.bind` and friends (*chaos*). diff --git a/plugin/cache/README.md b/plugin/cache/README.md index b961b04a5..d227ef6ce 100644 --- a/plugin/cache/README.md +++ b/plugin/cache/README.md @@ -77,7 +77,7 @@ If monitoring is enabled (via the *prometheus* plugin) then the following metric * `coredns_cache_served_stale_total{server}` - Counter of requests served from stale cache entries. Cache types are either "denial" or "success". `Server` is the server handling the request, see the -metrics plugin for documentation. +prometheus plugin for documentation. ## Examples diff --git a/plugin/reload/README.md b/plugin/reload/README.md index 2417357b4..05c6b712f 100644 --- a/plugin/reload/README.md +++ b/plugin/reload/README.md @@ -86,7 +86,7 @@ is already listening on that port. The process reloads and performs the followin 4. fail loading the new Corefile, abort and keep using the old process 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. In general be careful with assigning new port and expecting reload to work fully.