Why use statsd when graphite's Carbon aggregator can do the same job?

Question

I have been exploring the Graphite graphing tool for showing metrics from multiple servers, and it seems that the \'recommended\' way is to send all metrics data to StatsD first

Answer 1

Looks like carbon aggregator and statsd support disjoint set of features:

• statsd supports rate calculation and summation but does not support averaging values
• carbon aggregator supports averaging but does not support rate calculation.