# Process multiple Dead Letter Queues with one pipeline

**URL:** <https://discuss.elastic.co/t/process-multiple-dead-letter-queues-with-one-pipeline/253430>\
**Category:** Logstash\
**Created:** [October 27, 2020, 11:42am UTC](https://discuss.elastic.co/t/process-multiple-dead-letter-queues-with-one-pipeline/253430 "2020-10-27T11:42:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![michielw](https://avatars.discourse-cdn.com/v4/letter/m/48db29/32.png) [@michielw](https://discuss.elastic.co/u/michielw)\
**Post date:** [October 27, 2020, 11:42am UTC](https://discuss.elastic.co/t/process-multiple-dead-letter-queues-with-one-pipeline/253430/1 "2020-10-27T11:42:19Z")

</div>

In our Elastic environment we use multiple pipelines on a single Logstash instance. Also, we enabled the Dead Letter Queue on all these pipelines. On creating the pipeline to process events in the DLQs I noticed I need to specify the name of the pipeline I want to process.  
So, do I need to create a DLQ processing pipeline for each of the pipelines we have on our instance? Or is there a way to have one DLQ processing pipeline to handle all of them? In my opinion that would be a more efficient solution (as each pipeline will consume CPU and memory resources).

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [October 27, 2020, 1:12pm UTC](https://discuss.elastic.co/t/process-multiple-dead-letter-queues-with-one-pipeline/253430/2 "2020-10-27T13:12:17Z")

</div>

You can have multiple inputs in a pipeline.

```auto
input {
  dead_letter_queue {
    configuration 1
  }
  dead_letter_queue {
    configuration 2
  }
  dead_letter_queue {
    configuration N
  }
}

```

This way you can have all your dead letter queue processing in just one pipeline. You can also limit the resources for each pipeline if you use the `pipeline.workers` option in `pipelines.yml`.

---

<div class="post-metadata">

**Author:** ![michielw](https://avatars.discourse-cdn.com/v4/letter/m/48db29/32.png) [@michielw](https://discuss.elastic.co/u/michielw)\
**Post date:** [October 28, 2020, 2:11pm UTC](https://discuss.elastic.co/t/process-multiple-dead-letter-queues-with-one-pipeline/253430/3 "2020-10-28T14:11:38Z")

</div>

Tried it and it works perfectly this way. Thank you.

---

<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:** [November 25, 2020, 2:11pm UTC](https://discuss.elastic.co/t/process-multiple-dead-letter-queues-with-one-pipeline/253430/4 "2020-11-25T14:11:56Z")

</div>

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