From cd3a546179ebf3c23142d98023ff89309ebb6d49 Mon Sep 17 00:00:00 2001 From: Matthias Rampke Date: Thu, 20 Dec 2018 16:47:22 +0000 Subject: [PATCH] Clarify TTLs configuration remark I realized that "TTLs are applied" is ambiguous. Metrics don't only expire on receiving a sample, so mention that this is about the configuration. Signed-off-by: Matthias Rampke --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 16f2646..233e758 100644 --- a/README.md +++ b/README.md @@ -358,10 +358,10 @@ The value is a time duration with valid time units: "ns", "us" (or "µs"), "ms", "s", "m", "h". For example, `ttl: 1m20s`. `0` value is used to indicate metrics that do not expire. - TTLs are applied to each mapped metric name/labels combination whenever - new samples are received. This means that you cannot immediately expire a - metric only by changing the mapping configuration. At least one sample must - be received for updated mappings to take effect. + TTL configuration is stored for each mapped metric name/labels combination + whenever new samples are received. This means that you cannot immediately + expire a metric only by changing the mapping configuration. At least one + sample must be received for updated mappings to take effect. ## Using Docker