# Hard drive usage for monitoring logs too high

**URL:** <https://discuss.elastic.co/t/hard-drive-usage-for-monitoring-logs-too-high/309017>\
**Category:** Elasticsearch\
**Created:** [July 6, 2022, 1:27pm UTC](https://discuss.elastic.co/t/hard-drive-usage-for-monitoring-logs-too-high/309017 "2022-07-06T13:27:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kristofdc](https://avatars.discourse-cdn.com/v4/letter/k/3da27b/32.png) [@kristofdc](https://discuss.elastic.co/u/kristofdc)\
**Post date:** [July 6, 2022, 1:27pm UTC](https://discuss.elastic.co/t/hard-drive-usage-for-monitoring-logs-too-high/309017/1 "2022-07-06T13:27:56Z")

</div>

Our Azure Elasticsearch instance has a hard disk of 60 Gb.  
On our dev/acc environments, the hard disk took more than 55 Gb of space.  
Which resulted into a disk usage exceeded flood-stage-watermark, Kibana was not available and search didn't work.

We deleted the monitoring logs on the dev/acc environments and the problem was solved. It seems that the logs took more than 50 gb out of the 55 Gb on our hard disk:  
examples of monitoring indices:  
_.ds-.monitoring-beats-8-mb-yyyy.mm.dd-999999_  
_.ds-.monitoring-ent-search-8-mb-yyyy.mm.dd-999999_

How can we deleting monitoring logs automatically or modify some settings when they take too many place on the hard disk?

Thanks!

---

<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 3, 2022, 1:28pm UTC](https://discuss.elastic.co/t/hard-drive-usage-for-monitoring-logs-too-high/309017/2 "2022-08-03T13:28:38Z")

</div>

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