# How can we apply ILM to Stack Monitoring indices?

**URL:** <https://discuss.elastic.co/t/how-can-we-apply-ilm-to-stack-monitoring-indices/293231>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring, ilm-index-lifecycle-management\
**Created:** [December 30, 2021, 10:20pm UTC](https://discuss.elastic.co/t/how-can-we-apply-ilm-to-stack-monitoring-indices/293231 "2021-12-30T22:20:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Laurent\_Gauthier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/laurent_gauthier/32/64333_2.png) [@Laurent\_Gauthier](https://discuss.elastic.co/u/Laurent_Gauthier)\
**Post date:** [December 30, 2021, 10:20pm UTC](https://discuss.elastic.co/t/how-can-we-apply-ilm-to-stack-monitoring-indices/293231/1 "2021-12-30T22:20:22Z")

</div>

We are using Stack Monitoring on our Elastic Cloud clusters and this is proving very helpful. However, by default, the Stack Monitoring creates new indexes everyday (.monitoring-\*) and we have not found and easy way to change this. Index sizes vary but are always below 1 GB per day so we would like to apply an ILM policy to manage the number of indices.

It was suggested that we convert the monitoring indices to use datastreams but I would like to find instructions on how to do that since it does appear as a trivial task and is certainly not without risks of breaking something. Any other suggestion is welcome.

---

<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:** [January 27, 2022, 10:21pm UTC](https://discuss.elastic.co/t/how-can-we-apply-ilm-to-stack-monitoring-indices/293231/2 "2022-01-27T22:21:17Z")

</div>

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