graphite-dev team mailing list archive

[Michael Leinartas <question185158@xxxxxxxxxxxxxxxxxxxxx>]

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

Michael Leinartas posted a new comment:
I'd suggest using statsd (or some solution like it) rather than relying on carbon-aggregator.  carbon-aggregator was intended to create aggregated values from existing values already being persisted. So say,
production.web01.hits
production.web02.hits
production.web03.hits

can be aggregated into
production.all.hits

leaving 4 total metrics - 3 per-server metrics, and 1 aggregated metric

It is possible to aggregate a single metric by setting the 'from' and 'to' in aggregation-rules.conf to be the same, but you'd need to be more strict in metric naming to make sure the proper aggregation is applied (e.g. metrics ending in .count are summed, ending in .timer are averaged) and to ensure that metrics that dont need aggregation arent caught up in it improperly.
Note that if you want to try this out, you'll need to use trunk for a patch that fixes this use case.

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