You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your work. I'm currently relying on this statsd backend.
According to http://opentsdb.net/metrics.html , " something is a counter, or is naturally something that is a rate, don't convert it to a rate before sending it to the TSD. "
So, I'm wondering whether there is any specific reason to have this backend send counter rate?
Thanks
The text was updated successfully, but these errors were encountered:
Glad you find this backend useful. To be honest I copied the Graphite backend and modified for OpenTSDB. The counter versus rate occurred to me, but it is not clear to me how easily the counter can be supported within the statsd backend. It is easier to track a rate, as that is relatively stateless (i.e. for any given minute, need only keep track of the rate for that minute, whereas a counter persists from minute to minute and from what value does it start?) That said, if you can find how to change the code so it tracks the counter instead, submit a pull request and I will merge it in.
Hi,
Thanks for your work. I'm currently relying on this statsd backend.
According to http://opentsdb.net/metrics.html , " something is a counter, or is naturally something that is a rate, don't convert it to a rate before sending it to the TSD. "
So, I'm wondering whether there is any specific reason to have this backend send counter rate?
Thanks
The text was updated successfully, but these errors were encountered: