Hacker News Reader

Comment by bbrks | Hacker News Reader

As somebody new to both, are you able to elaborate on what telegraf/TICK provides that the collection of programs in the post does not?

I see lots of posts complaining about the stack in the post, but all of the alternatives posed don't really explain why.

View on HN

Telegraf and collectd do roughly the same thing. They run some plugins to get data and push the results to a given metrics sink. I asked because TICK (Telegraf, InfluxDB, Chronograf and Kapacitor) is a known solution and a fairly standard way to add elements of monitoring to your system.

> TICK (Telegraf, InfluxDB, Chronograf and Kapacitor) is a known solution and a fairly standard way to add elements of monitoring to your system.

Amusing that I've never heard of any of this but have heard and used collectd.

It's obviously no where near as common as a lamp stack or anywhere near common at all, so asking why it over something else is answered by "someone made it up so it's better".

Collectd is only one part here. Did you need a solution for inline processing/aggregation and alerting? If not, you wouldn't run into TICK. It's not common overall, because few environments need to go that far.

I don't get the comparison to LAMP popularity. Insects are more common than cars too. They're different things ¯\_(ツ)_/¯

I mentioned lamp as an example of an acronym and stack that would be more common to ask why it wasn't chosen. In retrospect that probably wasn't the ideal way of getting to my point that tick isn't a common stack so asking why not it because it's common seems weird.

> If not, you wouldn't run into TICK. It's not common overall, because few environments need to go that far.

That's my point though. The post I replied to acted as though everyone knows of and uses it, but provided no information on what makes it a better choice for such usecases.

Reply on news.ycombinator.com