# Viewing dead letter queue

**URL:** <https://discuss.elastic.co/t/viewing-dead-letter-queue/212710>\
**Category:** Logstash\
**Created:** [December 20, 2019, 9:00pm UTC](https://discuss.elastic.co/t/viewing-dead-letter-queue/212710 "2019-12-20T21:00:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard\_Neely](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@Richard\_Neely](https://discuss.elastic.co/u/Richard_Neely)\
**Post date:** [December 20, 2019, 9:00pm UTC](https://discuss.elastic.co/t/viewing-dead-letter-queue/212710/1 "2019-12-20T21:00:26Z")

</div>

Is there a good way to tail dead letter queue? It's a binary file so just using tail -f doesn't really work. I'm trying to track down some missing messages in a high volume system. I suspect they are hitting dlq but hard to find among other dlq items. If I send all my output to flat file it's just too much.

---

<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:** [January 17, 2020, 9:00pm UTC](https://discuss.elastic.co/t/viewing-dead-letter-queue/212710/2 "2020-01-17T21:00:31Z")

</div>

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