Having used the ELK Stack, which has been in existence for some time, we ask: is there space for another component in the Stack?
This is one of the biggest questions we think you'll have: where and how will Beats fit into the Elastic Stack? As we have already covered what Beats are, we have your answer covered, and this section that will provide you the answer to your question.
Beats has been added among the core components of the Stack due to the endless opportunities it creates when you use it. In the ELK Stack, you are bounded by the input plugins provided, via which only you can read the data. If you want to index operational data within Elasticsearch, such as transaction level information between multiple systems, Docker container statistics, Tomcat JMX metrics, or system-wide process level statistics, you would need to write a Logstash input plugin, which would then be used for such scenarios. For scenarios where you have multiple systems and you want...