# Logstash retries 404 instead of dropping - output stuck

**URL:** <https://discuss.elastic.co/t/logstash-retries-404-instead-of-dropping-output-stuck/319741>\
**Category:** Logstash\
**Created:** [November 24, 2022, 11:08am UTC](https://discuss.elastic.co/t/logstash-retries-404-instead-of-dropping-output-stuck/319741 "2022-11-24T11:08:20Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [November 24, 2022, 7:08pm UTC](https://discuss.elastic.co/t/logstash-retries-404-instead-of-dropping-output-stuck/319741/4 "2022-11-24T19:08:08Z")

</div>

You can cope with a limited outage of one output by using pipeline to pipeline communication with an [output isolator](https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.html#output-isolator-pattern) pattern.

If you want to drop data instead of using logstash's at-least-once delivery model then see [this post](https://discuss.elastic.co/t/logstash-multiple-pipelines-failure-with-persistent-queues/296520/2).

---

_[View the full topic](https://discuss.elastic.co/t/logstash-retries-404-instead-of-dropping-output-stuck/319741)._