Working with the ELK stack

Re:Working with the ELK stack by Karunamon on Friday February 06, 2015 @11:32AM (#9009753)

I would be seriously beginning to worry, were I working over at Splunk. I know the ES guys have said, over and over, that they're not gunning for Splunk customers but, as the ELK stack becomes a more mature tool, the reasons to use Splunk and pay their downright extortionate prices decrease more and more.

I'm assisting with a ~500GB/day cluster right now (with that number expected to quadruple in the next year or so), and ELK has proven to be an amazingly resilient and flexible tool.

[ Parent | on HN ]

Re:Working with the ELK stack by Iaks on Friday February 06, 2015 @01:05PM (#9010459)

I've worked with both systems quite a bit, and really like them both. The licensing obviously makes ELK a no-brainer for my personal use. But, to be fair to Splunk the average required knowledge for their end-user is significantly lower. For the crowd poking around here it seems obvious that ELK is the right choice, but when I am unleashing a team of helpdesk techs on a set of data I would probably have a much more nuanced consideration about the tools.

I'm kind of pointing out the obvious, but it's my two cents for whatever they're worth.

[ Parent | on HN ]