# Beat support for Message Queue output

**URL:** https://discuss.elastic.co/t/beat-support-for-message-queue-output/39567
**Category:** Beats
**Created:** [January 19, 2016, 4:36pm UTC](https://discuss.elastic.co/t/beat-support-for-message-queue-output/39567 "2016-01-19T16:36:27Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Nir\_Dothan](https://avatars.discourse-cdn.com/v4/letter/n/a587f6/32.png) [@Nir\_Dothan](https://discuss.elastic.co/u/Nir_Dothan)
#### Post date: [January 19, 2016, 4:36pm UTC](https://discuss.elastic.co/t/beat-support-for-message-queue-output/39567/1 "2016-01-19T16:36:27Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [January 20, 2016, 7:24am UTC](https://discuss.elastic.co/t/beat-support-for-message-queue-output/39567/2 "2016-01-20T07:24:05Z")

</div>

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 🙂

---

<div class="post-metadata">

### Author: ![megakid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/megakid/32/59227_2.png) [@megakid](https://discuss.elastic.co/u/megakid)
#### Post date: [January 20, 2016, 8:21am UTC](https://discuss.elastic.co/t/beat-support-for-message-queue-output/39567/3 "2016-01-20T08:21:52Z")

</div>

I would be very interested in either ActiveMQ or EventStore protocol support for packetbeat. I guess this comes under this topic.

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [January 20, 2016, 8:29am UTC](https://discuss.elastic.co/t/beat-support-for-message-queue-output/39567/4 "2016-01-20T08:29:40Z")

</div>

Best is to have a look at the discussion here: [https://github.com/elastic/filebeat/issues/132](https://github.com/elastic/filebeat/issues/132)

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [January 20, 2016, 8:31am UTC](https://discuss.elastic.co/t/beat-support-for-message-queue-output/39567/5 "2016-01-20T08:31:12Z")

</div>

@megakid If you refer to packetbeat supporting to read these protocols, I think this goes into an other topic. Here is a list of requested new protocols: [https://github.com/elastic/beats/labels/new%20protocol](https://github.com/elastic/beats/labels/new%20protocol)

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 9:56pm UTC](https://discuss.elastic.co/t/beat-support-for-message-queue-output/39567/6 "2017-07-05T21:56:34Z")

</div>


