# What's the best way to feed aggregated stats into Graphite?

**URL:** <https://discuss.elastic.co/t/whats-the-best-way-to-feed-aggregated-stats-into-graphite/90551>\
**Category:** Logstash\
**Created:** [June 22, 2017, 10:18pm UTC](https://discuss.elastic.co/t/whats-the-best-way-to-feed-aggregated-stats-into-graphite/90551 "2017-06-22T22:18:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![UnitedMarsupials](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/unitedmarsupials/32/19429_2.png) [@UnitedMarsupials](https://discuss.elastic.co/u/UnitedMarsupials)\
**Post date:** [June 22, 2017, 10:18pm UTC](https://discuss.elastic.co/t/whats-the-best-way-to-feed-aggregated-stats-into-graphite/90551/1 "2017-06-22T22:18:32Z")

</div>

When processing logs from a web-server for example, one is interested in _average_ throughput and the browser-type breakdowns for one's site, whereas the individual hits aren't all that interesting.

So, the `graphite` output plugin (which talks to `carbon-cache`-service) is not especially useful in this case -- what should I use instead? Is there anything, that can talk to `carbon-aggregator`-service, perhaps?

I know, there is a `statsd`-output -- anything else?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 26, 2017, 5:19am UTC](https://discuss.elastic.co/t/whats-the-best-way-to-feed-aggregated-stats-into-graphite/90551/2 "2017-06-26T05:19:39Z")

</div>

The aggregate Logstash plugin should also be helpful, but if we're talking about Graphite I'd probably go with statsd.

Ideally I'd use ES and Kibana for this, though.

---

<div class="post-metadata">

**Author:** ![UnitedMarsupials](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/unitedmarsupials/32/19429_2.png) [@UnitedMarsupials](https://discuss.elastic.co/u/UnitedMarsupials)\
**Post date:** [June 26, 2017, 8:15pm UTC](https://discuss.elastic.co/t/whats-the-best-way-to-feed-aggregated-stats-into-graphite/90551/3 "2017-06-26T20:15:38Z")

</div>

Statsd is realtime-only -- unlike Graphite's, its protocol does not even support timestamps. Which makes it dangerously useless for logs with timestamps, such as, for example, those listing web-hits from a CDN.

Not sure, how ES and Kibana would handle such logs...

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 27, 2017, 6:18am UTC](https://discuss.elastic.co/t/whats-the-best-way-to-feed-aggregated-stats-into-graphite/90551/4 "2017-06-27T06:18:56Z")

</div>

> Statsd is realtime-only -- unlike Graphite's, its protocol does not even support timestamps. Which makes it dangerously useless for logs with timestamps, such as, for example, those listing web-hits from a CDN.

Yes, that's a limitation of statsd.

> Not sure, how ES and Kibana would handle such logs...

Just fine since aggregations aren't pre-computed.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 25, 2017, 6:19am UTC](https://discuss.elastic.co/t/whats-the-best-way-to-feed-aggregated-stats-into-graphite/90551/5 "2017-07-25T06:19:01Z")

</div>

Closed on July 25, 2017, 6:19am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.