From e8c48d2663231bcfcddf680d7bd4fc5a545add3f Mon Sep 17 00:00:00 2001 From: DenysNahurnyi Date: Sat, 19 Oct 2019 14:22:09 +0300 Subject: [PATCH] Fix typos Signed-off-by: DenysNahurnyi --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 34fd0855..8649a876 100644 --- a/README.md +++ b/README.md @@ -170,7 +170,7 @@ instance. Even with `honor_labels: true`, the Prometheus server will attach an `instance` label if no `instance` label has been set in the first place. Therefore, if a metric is pushed to the Pushgateway without an instance label (and without instance label in the grouping key, see below), the -Pushgateway will export it with an emtpy instance label (`{instance=""}`), +Pushgateway will export it with an empty instance label (`{instance=""}`), which is equivalent to having no `instance` label at all but prevents the server from attaching one. @@ -215,7 +215,7 @@ be scraped at all anymore. (Prometheus knows only one timestamp per sample, there is no way to distinguish a 'time of pushing' and a 'time of scraping'.) -As there aren't any use cases where it would make sense to to attach a +As there aren't any use cases where it would make sense to attach a different timestamp, and many users attempting to incorrectly do so (despite no client library supporting this), the Pushgateway rejects any pushes with timestamps.