# Logstash and multiple outputs: how can I circumvent unreliable outputs?

**URL:** <https://discuss.elastic.co/t/logstash-and-multiple-outputs-how-can-i-circumvent-unreliable-outputs/51159>\
**Category:** Logstash\
**Created:** [May 27, 2016, 12:54pm UTC](https://discuss.elastic.co/t/logstash-and-multiple-outputs-how-can-i-circumvent-unreliable-outputs/51159 "2016-05-27T12:54:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ppuschmann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppuschmann/32/146751_2.png) [@ppuschmann](https://discuss.elastic.co/u/ppuschmann)\
**Post date:** [May 27, 2016, 12:54pm UTC](https://discuss.elastic.co/t/logstash-and-multiple-outputs-how-can-i-circumvent-unreliable-outputs/51159/1 "2016-05-27T12:54:50Z")

</div>

Hi,

in a test scenario (still using Logstash 1.5) we like to push logevents to two separate outputs.  
The first one is 'elasticsearch' the second one shall be 'redis'.

Right now we experience errors in the whole Logstash instance when one output is not available.

Are these blocking issues removed in newer versions of Logstash or is this a general weakness of the design?

Is there a way to circumvent this?  
Like having an output that drops events when the endpoint is not available?

---

<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:** [May 29, 2016, 1:11am UTC](https://discuss.elastic.co/t/logstash-and-multiple-outputs-how-can-i-circumvent-unreliable-outputs/51159/2 "2016-05-29T01:11:59Z")

</div>

This behaviour is intentional as LS, there is no way around it.

---

<div class="post-metadata">

**Author:** ![ppuschmann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppuschmann/32/146751_2.png) [@ppuschmann](https://discuss.elastic.co/u/ppuschmann)\
**Post date:** [May 30, 2016, 7:20am UTC](https://discuss.elastic.co/t/logstash-and-multiple-outputs-how-can-i-circumvent-unreliable-outputs/51159/3 "2016-05-30T07:20:18Z")

</div>

Hi @warkolm,

thank you very much for your answer.

I was kind of certain before this would be the answer. And it is. 😞

I'll have to find some different way to deliver these events.

---

<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 6, 2017, 4:55am UTC](https://discuss.elastic.co/t/logstash-and-multiple-outputs-how-can-i-circumvent-unreliable-outputs/51159/4 "2017-07-06T04:55:34Z")

</div>