# Limit ElasticSearch repetitive logs after exception

**URL:** <https://discuss.elastic.co/t/limit-elasticsearch-repetitive-logs-after-exception/279695>\
**Category:** Logstash\
**Created:** [July 27, 2021, 7:28am UTC](https://discuss.elastic.co/t/limit-elasticsearch-repetitive-logs-after-exception/279695 "2021-07-27T07:28:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stefan\_Speranta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefan_speranta/32/76864_2.png) [@Stefan\_Speranta](https://discuss.elastic.co/u/Stefan_Speranta)\
**Post date:** [July 27, 2021, 7:28am UTC](https://discuss.elastic.co/t/limit-elasticsearch-repetitive-logs-after-exception/279695/1 "2021-07-27T07:28:50Z")

</div>

Hi,

We have developed a project using Elastic, Logstash and Kibana as log management.  
After some site attacks one area of application got into endless loops of exceptions and filled Elastic with the same log massage again and again.

Is there a known way to limit this repetitive behavior with any upfront configuration or other approach?

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:** [August 24, 2021, 7:29am UTC](https://discuss.elastic.co/t/limit-elasticsearch-repetitive-logs-after-exception/279695/2 "2021-08-24T07:29:49Z")

</div>

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