# Limiting Repetitive Log Messages

**URL:** <https://discuss.elastic.co/t/limiting-repetitive-log-messages/215844>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [January 21, 2020, 8:53am UTC](https://discuss.elastic.co/t/limiting-repetitive-log-messages/215844 "2020-01-21T08:53:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![natey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/natey/32/61112_2.png) [@natey](https://discuss.elastic.co/u/natey)\
**Post date:** [January 21, 2020, 8:53am UTC](https://discuss.elastic.co/t/limiting-repetitive-log-messages/215844/1 "2020-01-21T08:53:08Z")

</div>

Hi,

We have developed a private PaaS, using Elastic+Filebeat+Logstash+Kibana as centralized logs management.  
One micro-service that got into endless lop of exceptions filled Elastic disk with the same log massage so Elastic become red.

Is there a known way to deal with issues like this from Elastic stack perspective?  
Not just with clean up by the curator, cause that won't solve the root cause.

---

<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 18, 2020, 8:53am UTC](https://discuss.elastic.co/t/limiting-repetitive-log-messages/215844/2 "2020-02-18T08:53:14Z")

</div>

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