Hard drive usage for monitoring logs too high

Elastic Stack Elasticsearch
1

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!

2

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