Documentation shows that Redis output is deprecated, and I didn't see Kafka at all. Is there an architectural reason why I would not want to use a message queue between Beat and the Logstash indexer? Are there any plans to support message queues in the future?

Beat support for Message Queue output

warkolm (Mark Walkom) January 20, 2016, 7:24am 2

We still recommend the use of a broker, at least until the next major release of Logstash that will contain one.

I'll let the Beats team comment more

Topic		Replies	Views
Using RabbitMq as broker between Beats and Logstash Beats	28	821	June 16, 2024
Libbeat kafka output Beats	4	1608	July 5, 2017
Considering using L4 or kafka Logstash	2	205	July 3, 2023
Filebeat with Redis or just logstash? Beats	7	5200	December 7, 2016
Beats protocol Beats	7	25391	July 5, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Beat support for Message Queue output

Related topics