mirror of
https://github.com/prometheus/statsd_exporter.git
synced 2024-11-26 09:11:01 +00:00
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 <mr@soundcloud.com>
This commit is contained in:
parent
7364c6fe44
commit
cd3a546179
1 changed files with 4 additions and 4 deletions
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in a new issue