# Questions about dead letter queue

**URL:** <https://discuss.elastic.co/t/questions-about-dead-letter-queue/110798>\
**Category:** Logstash\
**Created:** [December 8, 2017, 7:43am UTC](https://discuss.elastic.co/t/questions-about-dead-letter-queue/110798 "2017-12-08T07:43:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![RobBavey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robbavey/32/20421_2.png) [@RobBavey](https://discuss.elastic.co/u/RobBavey)\
**Post date:** [December 15, 2017, 12:38pm UTC](https://discuss.elastic.co/t/questions-about-dead-letter-queue/110798/2 "2017-12-15T12:38:14Z")

</div>

Hi @tgxworld,

Currently, the DLQ logs do not get deleted automatically - this is a feature that will be added in a future Logstash release.

A new DLQ log file is created either a) when Logstash is started up, or b) when a new event would cause the log file to be larger than the 'maximum segment size' - this is currently set to 10MB.

To view the Dead Letter Queue there is a [dead letter queue input plugin](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-dead_letter_queue.html). This can be processed like any other Logstash input - initially you can pipe to stdout, or similar, using the rubydebug filter (with metadata enabled) to determine the errors. Then you can use the mutate filter to remove any mapping errors (as shown [here](https://www.elastic.co/guide/en/logstash/current/dead-letter-queues.html#processing-dlq-events))

The `commit_offset` flag when set to `true` will cause the last processed DLQ entry to be stored in the .sincedb file stored in the `${path.data}/plugins/inputs/dead_letter_queue/${pipeline.id}` folder (pipeline\_id will be `main` unless it has been manually set. If the `commit_offset` flag is set to `false`, these offsets will not be stored.

Thanks!

Rob

---

_[View the full topic](https://discuss.elastic.co/t/questions-about-dead-letter-queue/110798)._