Skip to content
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

Why send counter_rate? #1

Open
mocheng opened this issue Feb 17, 2013 · 2 comments
Open

Why send counter_rate? #1

mocheng opened this issue Feb 17, 2013 · 2 comments

Comments

@mocheng
Copy link

mocheng commented Feb 17, 2013

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

@emurphy
Copy link
Collaborator

emurphy commented Feb 19, 2013

Hi,

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.

Emmet

@mocheng
Copy link
Author

mocheng commented Feb 21, 2013

I'm still digging the details. It seems that OpenTSDB can calculate rate by itself, if statsd just reported counters.

As the attached image, just select the "Rate" checkbox and OpenTSDB show the rate result.

QQ20130221-2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants