mirrors/statsd_exporter
1
0
Fork 1
mirror of https://github.com/prometheus/statsd_exporter.git synced 2024-11-26 17:21:01 +00:00
Code Issues Projects Releases Packages Wiki Activity

Clarify TTLs configuration remark

Browse source 
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:
Matthias Rampke 2018-12-20 16:47:22 +00:00
parent 7364c6fe44
commit cd3a546179
No known key found for this signature in database
GPG key ID: 2CDE413A9BD0A5BC
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -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 "ms", "s", "m", "h". For example, `ttl: 1m20s`. `0` value is used to indicate
metrics that do not expire. metrics that do not expire.
TTLs are applied to each mapped metric name/labels combination whenever TTL configuration is stored for each mapped metric name/labels combination
new samples are received. This means that you cannot immediately expire a whenever new samples are received. This means that you cannot immediately
metric only by changing the mapping configuration. At least one sample must expire a metric only by changing the mapping configuration. At least one
be received for updated mappings to take effect. sample must be received for updated mappings to take effect.
## Using Docker ## Using Docker