aggregation over 60s creates 6 datapoints per minute

Asked by Steve Akers

I have an aggregation setup that is basically <metric>.all.count (60) = sum <metric>.*.count. While this results in the correct 1min values, graphite is displaying 6 datapoints per minute. This means I get value, null, null, null, null, null. This creates a problem when using the aggregated metric in comparison to other metrics. I have to summarize it over 1 min in order to do these calculations correctly. Is this a bug, or am I doing something wrong?


Question information

English Edit question
Graphite Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Steve Akers (steve-akers) said :

Could this be because my retention policy for current month data is at 10s?

Revision history for this message
Michael Leinartas (mleinartas) said :

Yeah, your storage-schemas must match the rate at which you're aggregating. You can either change the aggregation to (10) or adjust your storage-schemas and either remove the existing whisper files or resize them with

Can you help with this problem?

Provide an answer of your own, or ask Steve Akers for more information if necessary.

To post a message you must log in.