# Report DLQ's max\_queue\_size\_in\_bytes in logstash API

**URL:** <https://discuss.elastic.co/t/report-dlqs-max-queue-size-in-bytes-in-logstash-api/164585>\
**Category:** Logstash\
**Created:** [January 17, 2019, 8:13am UTC](https://discuss.elastic.co/t/report-dlqs-max-queue-size-in-bytes-in-logstash-api/164585 "2019-01-17T08:13:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sarfaraz\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@Sarfaraz\_Ahmad](https://discuss.elastic.co/u/Sarfaraz_Ahmad)\
**Post date:** [January 17, 2019, 8:13am UTC](https://discuss.elastic.co/t/report-dlqs-max-queue-size-in-bytes-in-logstash-api/164585/1 "2019-01-17T08:13:17Z")

</div>

logstash's monitoring API only reports the bytes used in the DLQ.  
If it were to report the configured bytes for the DLQ like what it does with the persistent queue, then my monitoring tool can figure out what percentage of the DLQ is being consumed and I can avoid telling my monitoring tool what the current configured size of my DLQ is. The monitoring tool would gather that from the logstash API.

Please opine and/or create a bug at the logstash github repo.

---

<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:** [February 14, 2019, 8:13am UTC](https://discuss.elastic.co/t/report-dlqs-max-queue-size-in-bytes-in-logstash-api/164585/2 "2019-02-14T08:13:23Z")

</div>

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