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

Statsd counter float values #556

Closed
panda87 opened this issue Jan 20, 2016 · 1 comment · Fixed by #561
Closed

Statsd counter float values #556

panda87 opened this issue Jan 20, 2016 · 1 comment · Fixed by #561
Labels
bug unexpected problem or unintended behavior

Comments

@panda87
Copy link

panda87 commented Jan 20, 2016

Hi

I'm using statsd plugin to collect the consul metrics, but since the last version of consul it seems that part of the metrics (counters) are float and not int64.
For my case, i'm loosing a big amount of data just because of counters can't parse floats values.

My simple solution as I see it, is that in case of counter floats or any other object, try to cast to int64 and throw log that explain that the metrics may not be accurate and suggest to change the metrics type.

Below is the error im getting,

2016/01/18 17:17:47 Error: parsing value to int64: consul.memberlist.udp.sent:183.000000|c
2016/01/18 17:17:47 Error: parsing value to int64: consul.memberlist.udp.received:60.000000|c
2016/01/18 17:17:47 Error: parsing value to int64: consul.memberlist.udp.sent:183.000000|c
2016/01/18 17:17:47 Error: parsing value to int64: consul.memberlist.udp.received:60.000000|c
2016/01/18 17:17:47 Error: parsing value to int64: consul.memberlist.udp.sent:183.000000|c
2016/01/18 17:17:48 Error: parsing value to int64: consul.memberlist.udp.sent:69.000000|c

Thanks
D.

@panda87
Copy link
Author

panda87 commented Jan 21, 2016

@sparrc you are the man! thank you very much! I really appreciate your effort

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants