graphite-dev team mailing list archive

[Nicholas Leskiw <question218688@xxxxxxxxxxxxxxxxxxxxx>]

Question #218688 on Graphite changed:
https://answers.launchpad.net/graphite/+question/218688

    Status: Open => Answered

Nicholas Leskiw proposed the following answer:
Graphite averages by default when rolling up data into lower precision.
If you want to change that behavior, a) use the whisper-resize.py (there
may be another one that does it easier, on a mobile cant check) to edit
the existing files AND b) edit storage-aggregation.conf to sum those
metrics that are counts.  (Much like storage-schemas.conf)

It was originally 'avg' because graphite was used primarily for latency
tracking -  doesn't make sense to sum latencies.


-Nick

On Jan 8, 2013, at 8:41 PM, gyre007
<question218688@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Question #218688 on Graphite changed:
> https://answers.launchpad.net/graphite/+question/218688
> 
> gyre007 gave more information on the question:
> Strange thing is when I try to graph nr requests/s by using the
> following formula:
> 
> scaleToSeconds(derivative(stats.app01.live.staging.nginx.handles),1)
> 
> Graphite DOES display the rate correctly regardless of time range ie. it
> does display 1.2req/s even if the time range is > or < 12 hours.
> 
> -- 
> You received this question notification because you are a member of
> graphite-dev, which is an answer contact for Graphite.
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~graphite-dev
> Post to     : graphite-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~graphite-dev
> More help   : https://help.launchpad.net/ListHelp

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.