# Back pressure and persistent queue

**URL:** <https://discuss.elastic.co/t/back-pressure-and-persistent-queue/146590>\
**Category:** Logstash\
**Created:** [August 29, 2018, 11:27pm UTC](https://discuss.elastic.co/t/back-pressure-and-persistent-queue/146590 "2018-08-29T23:27:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kernelpanic](https://avatars.discourse-cdn.com/v4/letter/k/c89c15/32.png) [@kernelpanic](https://discuss.elastic.co/u/kernelpanic)\
**Post date:** [August 29, 2018, 11:27pm UTC](https://discuss.elastic.co/t/back-pressure-and-persistent-queue/146590/1 "2018-08-29T23:27:49Z")

</div>

Hello all,

From the documentation on persistent queues it seems to be saying only the beats framework inputs are protected - if I want my non-beats inputs to be protected from back pressure (e.g. syslogs) then do I need to implement another messaging solution such as Kafka?

Thanks for any advice

---

<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:** [September 26, 2018, 11:27pm UTC](https://discuss.elastic.co/t/back-pressure-and-persistent-queue/146590/2 "2018-09-26T23:27:51Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.