Statsd_exporter: bug in TTL parameter?

31 views
Skip to first unread message

Cedric Den Haese

unread,
Jul 7, 2019, 9:18:44 AM7/7/19
to Prometheus Developers
Hi everyone,

While planning to use the statsd_exporter to collect metrics from short-lived jobs, I was looking for a way to expire metrics that haven't been updated for a certain period.
Reading the statsd_exporter docs, I thought this might be configured by using the provided TTL parameter.

However, it seems that setting this parameter does not create the expected behavior.
For example, if I set the TTL to 10 sec, I would expect metrics that aren't updated within 10 seconds to be deleted.
The actual behavior shows that all metrics are deleted 10 seconds after they have been created, regardless of whether they were updated or not.
I have attached a screen capture as an example.

Is this a bug or is this behavior to be expected?

I have already adapted the source code locally to create the behavior I expect.
Should it actually be a bug, I can create a PR for it in the GitHub repo
statsd_exporter_ttl_bug.mp4

Matthias Rampke

unread,
Jul 8, 2019, 4:03:37 AM7/8/19
to Cedric Den Haese, Prometheus Developers
The video doesn't open for me, but what you describe does indeed seem wrong. Please do send a PR!

/MR

--
You received this message because you are subscribed to the Google Groups "Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/eaa09de7-3fb5-430e-a5ad-b3f512c5d815%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages