Graphite

Graphite problem with long values. I found them stored as decimal

Asked by jonathan

Hi,

I found the next issue when I built my graphics using the Graphite API.

I've configured Logstash to send data to Graphite storage system via JMX plugin.
The polling frequency was set to 30 seconds.

The issue is that I found long type values stored as decimal in Graphite.

Also, I found this questions in StackOverflow which doesn't have an accepted answer:

http://stackoverflow.com/questions/13019126/graphite-does-not-graph-values-correctly-when-using-long-durations

and I tried to use the summarize() function suggested in one of the comments in the post but still the same problem.

Running whisper-fetch I get the following output:

# whisper-fetch --pretty MessagesDropped.wsp
Tue Sep 9 07:50:00 2014 0.100000
Tue Sep 9 07:55:00 2014 0.100000

How can I solve this issue?

Any help would be appreciated.

Thanks

Question information

Language:
English Edit question
Status:
Solved
For:
Graphite Edit question
Assignee:
No assignee Edit question
Solved by:
Jason Dixon
Solved:
Last query:
Last reply:
Revision history for this message
Jason Dixon (jason-dixongroup) said : 		#1

What is your storage schema for this metric?

Revision history for this message
jonathan (jonsmith7777) said : 		#2

# cat /etc/carbon/storage-schemas.conf
[carbon]
pattern = ^carbon\.
retentions = 60:90d

[default_1min_for_1day]
pattern = .*
retentions = 5s:5m, 30s:1h, 5m:7d, 15m:30d, 1h:3y

Revision history for this message
Best Jason Dixon (jason-dixongroup) said : 		#3

Your highest precision retention should match your polling frequency. Because you have a 5s:5m retention level, many of your "buckets" are being rolled up into the 30s:1h as "none", causing your original data to be averaged down. I explained some of this here:

http://obfuscurity.com/2012/04/Unhelpful-Graphite-Tip-9

If you're going to continue polling every 30s, then remove that 5s:5m from your policy and restart your carbon-cache. If your data is all bad you might as well delete your Whisper files too. Otherwise you'll want to do a whisper-resize to match your new retention policy.

Revision history for this message
jonathan (jonsmith7777) said : 		#4

Thanks Jason Dixon, that solved my question.