title: Why use statsd when graphite's Carbon aggregator can do the same job?
body: <p>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. StatsD aggregates the data and sends it to graphite (or rather, Carbon).</p>
  
  <p>In my case, I want to do simple aggregations like sum and average on metrics across servers and plot that in graphite. Graphite comes with a Carbon aggregator which can do this.</p>
  
  <p>StatsD does not even provide aggregation of the kind I am talking about. </p>
  
  <p>My question is - should I use statsd at all for my use case? Anything I am missing here?</p>