Splunk vs ELK - Managing Production Logs

Question

I am working on a system that runs HPC on a grid every day. There are many servers, services and applications (Windows, Linux, IIS, Apache, Websphare, SQL, Mongo, .Net, Python, C ++)

It starts once a day.

I am very familiar with ELK. I especially like how elastic work as a database and its features: percolator, scoring system, Rest API, etc.

Recently I heard about Splunk, I studied it, and it looks very good.

Allows you to allocate $ cost

What would be the best solution for a non-cloud basic solution that would create a huge number of magazines in about 4 hours a day and could be stressful during that time?

Answer 1

Let me summarize this for you:

Splunk is a very powerful, mostly indoor solution, expensive and if all you need is a “super grap”, then it is really too expensive for this use case.

ELK - License fees are not incurred, but you end up spending $ on creating various functions, right away if you already know that you need N functions or gradually and over time, when users start to demand functions that ELK does not have.

Based on your requirement, I suggest you go with splunk.

PS If you want to see a detailed comparison, please look at the post .