integral-functions for the long period are incorrect

I think the problem is that your older data in lower precision archives is averaged when you probably want it summed. If you are on a recent trunk checkout or 0.9.9 you can configure the aggregation method whisper uses to rollup datapoints into lower precision archives. To do this you can GET the url http://graphite/metrics/set-metadata?metric=foo.bar.baz&key=aggregationMethod&value=sum

You can verify it with:

http://graphite/metrics/get-metadata?metric=foo.bar.baz&key=aggregationMethod

Note that this will only affect future aggregations, it cannot recompute the current aggregate values. You can also change it en masse by POSTing application/json data like this to the set-metadata url:

{
  "operations": [
    {"metric": "foo.bar.baz", "key": "aggregationMethod", "value": "sum"},
    {"metric": "foo.bar.baz2", "key": "aggregationMethod", "value": "sum"},
    ...
  ]
}

In order to make sure metrics created in the future have the proper aggregationMethod, create a /opt/graphite/conf/storage-aggregation.conf file. It works the exact same way storage-schemas.conf does except instead of specifying 'retentions' for a set of metrics, you define 'aggregationmethod' and/or 'xfilesfactor'. For example:

[latency-metrics]
pattern = .*responseTime
aggregationmethod = average

[everything-else]
match-all = true
aggregationmethod = sum

Again this only works with 0.9.9 or recent trunk. I hope that helps.

Hi Chris,
Thanks for your answer.

If I understand correctly, by using the specified method I wouldn't be able to check the "usual" graphics (I mean "target=series" without "integral" or "summarize")?

The thing is that I forgot to mention that we also do introspecting of the graphics (not the integral values)
so in addition to the usecases above we also do:

target=series1&from=-1month
target=series2&from=-1year

etc.

Could I use your method and don't break smth in my data?

Ivan.

I haven't checked the code thoroughly, but it seems to me that it might be done on-the-fly:

webapp/graphite/render/functions.py
def integral(requestContext, seriesList):
...
current += val

If we could check that the "val" is not from the 1m data, but from the 5m data (or 15m data) we could multiply it by the needed number and get the correct answer.

I mean smth like that (pseudocode):
...
current += val * multiplier(timeseries)
...

def multiplier(timeseries):
      if timeseries = "5m":
             return 5
      elif timeseries = "15m":
             return 15

      ....
      elif timeseries = "1y":
             return 60 * 24 * 356;

Surely, it can be done in a more accurate way, I just made it so rough to make my idea clear.

The methods I outlined change the way whisper aggregates data as it rolls into lower precision archives, so it changes what aggregate values get stored. The summarize() function lets you change how the rendering buckets datapoints and as long as your data is stored correctly (ie. you probably want to aggregate your counters with sum instead of average) then it should give you what you want. But again changing aggregationMethod will only affect future aggregations and thus won't affect any existing aggregated data. So yes I would change the aggregationMethods and use summarize. The rendering code isn't aware of aggregation configurations so we can't do what you suggest of multiplying the value based on the aggregation config.