# Setting different ilm policy based on index name

**URL:** <https://discuss.elastic.co/t/setting-different-ilm-policy-based-on-index-name/234497>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 27, 2020, 9:15am UTC](https://discuss.elastic.co/t/setting-different-ilm-policy-based-on-index-name/234497 "2020-05-27T09:15:01Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\
**Post date:** [May 27, 2020, 12:36pm UTC](https://discuss.elastic.co/t/setting-different-ilm-policy-based-on-index-name/234497/4 "2020-05-27T12:36:33Z")

</div>

I still get

```
"type" : "illegal_argument_exception",
        "reason" : "index.lifecycle.rollover_alias [filebeat-cisco] does not point to index [filebeat-cisco-2020.05.27]"

```

but i think adding -000001 to index will resolve the issue

> [@Index lifecycle error - illegal\_argument\_exception: index.lifecycle.rollover\_alias](https://discuss.elastic.co/t/index-lifecycle-error-illegal-argument-exception-index-lifecycle-rollover-alias/207900):
>
> Hello Team, Could you please help me with sorting out the following error while implementing ILM? Referred link [https://www.elastic.co/guide/en/elasticsearch/reference/7.4/getting-started-index-lifecycle-management.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.4/getting-started-index-lifecycle-management.html) Index lifecycle error illegal\_argument\_exception: index.lifecycle.rollover\_alias [temprule] does not point to index [templogs-2019.11] Current action rollover Failed step check-rollover-ready Current phase hot Show phase definition { "index.blocks.read\_only\_allow\_de…

---

_[View the full topic](https://discuss.elastic.co/t/setting-different-ilm-policy-based-on-index-name/234497)._