# How to monitor/identify retry result with output elasticsearch

**URL:** <https://discuss.elastic.co/t/how-to-monitor-identify-retry-result-with-output-elasticsearch/258681>\
**Category:** Logstash\
**Created:** [December 15, 2020, 8:28am UTC](https://discuss.elastic.co/t/how-to-monitor-identify-retry-result-with-output-elasticsearch/258681 "2020-12-15T08:28:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![loker](https://avatars.discourse-cdn.com/v4/letter/l/9fc29f/32.png) [@loker](https://discuss.elastic.co/u/loker)\
**Post date:** [December 15, 2020, 8:28am UTC](https://discuss.elastic.co/t/how-to-monitor-identify-retry-result-with-output-elasticsearch/258681/1 "2020-12-15T08:28:00Z")

</div>

Hello there,

Recently i meet some warning about es reject caused by queue exceed 200 limit.  
According to its retry policy for es output plugin, it should retry indefinitely for this kind of error(429).

But i don't know how to identify whether all retry is been processed successfully or not.  
In logstash node stats api, i see no valid information about this.

---

<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 12, 2021, 8:28am UTC](https://discuss.elastic.co/t/how-to-monitor-identify-retry-result-with-output-elasticsearch/258681/2 "2021-01-12T08:28:27Z")

</div>

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