The Elastic Stack: Future of ELK Platform

Re:The Elastic Stack: Future of ELK Platform by willejs on Thursday February 18, 2016 @05:09AM (#11124755)

So logstash V5, is that a rewrite in go? I say this because it seems all their other tooling is now written in go, and also, logstash agent and server are very resource intensive in jruby. If theres a v5 alpha, which isnt on github, is it not open source?

[ Parent | on HN ]

Re:The Elastic Stack: Future of ELK Platform by gerhardhaering on Thursday February 18, 2016 @06:14AM (#11125014)

Apparently all they've announced is that they'll release all their products in lockstep with a unified version number from now on.

I myself have hoped for a Go rewrite of Logstash for a long time, but there are apparently no plans for this. They are creating lightweight forwarders with their *beats, though. But they are only for forwarding to ElasticSearch, not a general log pipeline processor like Logstash.

FWIW there is a thing that's like Logstash in Go, it's Heka by Mozilla. I am very fond of it, but for some reason not many people seem to be aware of it or deploy it.

[ Parent | on HN ]

Re:The Elastic Stack: Future of ELK Platform by LeoHexspoor on Thursday February 18, 2016 @07:44AM (#11125328)

They have a couple of outputs from *beats though, not only ElasticSearch. Besides ElasticSearch there are outputs to console, file, Logstash and a deprecated Redis output.

[ Parent | on HN ]

Re:The Elastic Stack: Future of ELK Platform by packetized on Friday February 19, 2016 @02:35AM (#11132179)

I've been beating the drum for Heka ever since I found it.

[ Parent | on HN ]