# About the ILM policy implented and on the post observations

**URL:** <https://discuss.elastic.co/t/about-the-ilm-policy-implented-and-on-the-post-observations/351851>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [January 26, 2024, 6:02am UTC](https://discuss.elastic.co/t/about-the-ilm-policy-implented-and-on-the-post-observations/351851 "2024-01-26T06:02:13Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 27, 2024, 5:08am UTC](https://discuss.elastic.co/t/about-the-ilm-policy-implented-and-on-the-post-observations/351851/3 "2024-01-27T05:08:04Z")

</div>

> [@yago82](#):
>
> Hi,
> 
> This index is not managed by the ILM policy you have in place, which is why it's not being rolled over or deleted.
> 
> If you want to apply your ILM policy to this index, you can do so by updating the index settings.
> 
> ```auto
> PUT /filebeat-8.11.1/_settings
> {
> "index.lifecycle.name": "filebeat"
> }
> 
> ```
> 
> Regards

Hello,

Thank you for the response. Will test and update here on the same thread.

Thanks,

---

_[View the full topic](https://discuss.elastic.co/t/about-the-ilm-policy-implented-and-on-the-post-observations/351851)._