# ILM Policy and Filebeat versions

**URL:** <https://discuss.elastic.co/t/ilm-policy-and-filebeat-versions/226095>\
**Category:** Elasticsearch\
**Created:** [April 1, 2020, 5:07pm UTC](https://discuss.elastic.co/t/ilm-policy-and-filebeat-versions/226095 "2020-04-01T17:07:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![t3fsx](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@t3fsx](https://discuss.elastic.co/u/t3fsx)\
**Post date:** [April 1, 2020, 5:07pm UTC](https://discuss.elastic.co/t/ilm-policy-and-filebeat-versions/226095/1 "2020-04-01T17:07:08Z")

</div>

My setup is fairly simple. I use Filebeat, with all the default options to send to Elastic Cloud. My cluster is sized with 200GB.

I see that each update of Filebeat is creating it's own ILM policy, and there's also an umbrella policy (called simply filebeat) that covers all indices.

Where should I perform my changes? Is it safe to assume the "filebeat" policy covers and takes precedence over the "version specific" versions?

Example below:

 ![Screenshot 2020-04-01 at 18.06.31](https://us1.discourse-cdn.com/elastic/original/3X/e/b/eb76f83def034c8cff33b081928955b291e2b859.png)

---

<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:** [April 29, 2020, 5:07pm UTC](https://discuss.elastic.co/t/ilm-policy-and-filebeat-versions/226095/2 "2020-04-29T17:07:09Z")

</div>

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