Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

An ELK stack is definitely a lot easier and straight forward to setup. Since we need to support a dozen or so teams with varying performance considerations we found that logstash left a lot to be desired. In the end fluentd performed well and gave us a lot of flexibility.



> we found that logstash left a lot to be desired. In the end fluentd performed well and gave us a lot of flexibility.

Would you mind providing more details about why you felt that Logstash was lacking?


I'd like your view from the trenches regarding Logstash vs Fluentd, specifically why it's better for 12+ teams? I'm having to make a similar decision myself and would enjoy your insight! Thanks


(Disclaimer: I am a Fluentd maintainer)

Here are some comparisons out in the wild (Note: neither of them is a Logstash or Fluentd maintainer afaik)

- http://jasonwilder.com/blog/2013/11/19/fluentd-vs-logstash/

- https://blog.deimos.fr/2014/05/13/logstash-vs-fluentd/

Also, if you have any question or doubt about Fluentd, please feel free to email me at kiyoto@treasure-data.com




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: