# What's the correct ILM setup for .monitoring-\*-7 indices?
**URL:** https://discuss.elastic.co/t/whats-the-correct-ilm-setup-for-monitoring-7-indices/318398
**Category:** Elasticsearch
**Created:** [November 8, 2022, 8:38am UTC](https://discuss.elastic.co/t/whats-the-correct-ilm-setup-for-monitoring-7-indices/318398 "2022-11-08T08:38:15Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@alytkowski](https://discuss.elastic.co/u/alytkowski)
#### Post date: [November 8, 2022, 8:38am UTC](https://discuss.elastic.co/t/whats-the-correct-ilm-setup-for-monitoring-7-indices/318398/1 "2022-11-08T08:38:15Z")
As per title, what's the correct ILM setup for the .monitoring-\*-7 indices? By default, they rollover every day and delete after 7 days. However, I need them to delete much faster, because in my small ELK setup, these indices are taking a lot of space and I have to delete them manually. I applied a policy to the templates, but then, the indices threw errors like "index rollover alias is empty or not defined". I tried to follow steps from some other thread, where it was advised to delete all indices except for the "todays", edit settings for these indices and add rollover alias. So I set this to ".monitoring-beats-7" (and for es, logstash and kibana respectively), but then I encountered "index rollover alias does not point to alias".
The documentation doesn't really explain how to do this, can someone please explain?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 6, 2022, 8:38am UTC](https://discuss.elastic.co/t/whats-the-correct-ilm-setup-for-monitoring-7-indices/318398/2 "2022-12-06T08:38:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.