11

I see the combination statsd + telegraf + influxdb used all the time.

  • Statsd collects, aggregates and forwards metrics
  • Telegraf aggregates and forwards metrics

Why not use just the statsd (without telegraf) to aggregate and forward metrics? What is the added benefit of including telegraf?

andree
  • 3,084
  • 9
  • 34
  • 42
  • 2
    telegraf is a plugin based solution and has 4 concepts of distinct plugins. https://github.com/influxdata/telegraf/tree/master/plugins (See plugins for inputs and output). Due to the capabilities telegraf provides (T under TICK stack), it's better to use a plugin based solution. Telegraf also collects metrics using it's core or available input plugins. – AKS Feb 22 '17 at 07:38

1 Answers1

2

The last update to Etsy's statsd project was in 2016. One advantage of using telegraf is that it is an active project. Since telegraf has a Statsd plugin, it's possible that you don't need both.

righdforsa
  • 179
  • 1
  • 8
  • The statsd plugin doesn't replace statsd does it? Doesn't it just allow statsd to pipe information into telegraf? Maybe it does actually replace it... – Joe Phillips Feb 19 '20 at 20:05
  • Statsd latest commit was [on Aug 27, 2020](https://github.com/statsd/statsd/commit/9cf77d87855bcb69a8663135f59aa23825db9797). Just saying that is not _this_ old. – Eduardo Mar 25 '21 at 10:38