-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[statsd input plugin] documentation seems wrong about default value of delete_timings #1893
Comments
delete_timings
I don't even understand what |
delete_timings deletes it from Telegraf's internal cache, it obviously does no modification on the output plugins. It's important to understand the concept behind |
@sparrc Ok, it deletes it from cache when the value has been sent. Then why wouldn't it delete it then? What would be the reason behind non-deleting everything? |
I guess if you wanted the accumulated metrics in InfluxDB since runtime. I think I would also agree that the defaults should be |
The doc says:
But with no
delete_timings
option set, I was having timings not deleted, and sent at every interval. With the option set totrue
, the desired behavior is happening. I guess that it's only the documentation that got the default value wrong.BTW, I wonder why those options are
false
by default, since this is a very weird default... I never used etsy's statsd, but if I'm not mistaken, the "delete" way is the canonical way. It is even weirder to have values increment in influxdata's implementation, because with InfluxDB as the storage, it is so easy to sum values, get their mean or whatever, and this is easier if the raw, "interval deleted" values are stored, not the incremented ones.The text was updated successfully, but these errors were encountered: