graphite-dev team mailing list archive

[Michael Leinartas <question193500@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

Michael Leinartas proposed the following answer:
That example will result in a value of 1. The aggregationMethod setting
only influences the way in which aggregations happen when points move
from a higher resolution to a lower resolution at retention boundaries.

For instance, for a retention config of 10s:1d, 60s:7d (in storage-
schemas.conf)

Sending:
my.event 1 1334217480
my.event 1 1334217490
my.event 1 1334217500
my.event 1 1334217510
my.event 1 1334217520
my.event 1 1334217530


Will result in those 5 points being stored for 1 day. After 1 day, with aggregationMethod=sum, only this point will be available:
my.event 6 1334217480

With aggregationMethod=avg (the default), it will instead be
my.event 1 1334217480


In short, multiple points sent during the time bucket lining up with your highest resolution (say 1334217480 to 1334217489 seconds) will be overwritten and only the last one kept. If you need to do aggregation it should either be done by the sender or by an external process (statsd being the most common).

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