# Illegal\_argument\_exception: index.lifecycle.rollover\_alias does not point to index

**URL:** <https://discuss.elastic.co/t/illegal-argument-exception-index-lifecycle-rollover-alias-does-not-point-to-index/247089>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [September 1, 2020, 12:30pm UTC](https://discuss.elastic.co/t/illegal-argument-exception-index-lifecycle-rollover-alias-does-not-point-to-index/247089 "2020-09-01T12:30:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sgreszcz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sgreszcz/32/46322_2.png) [@sgreszcz](https://discuss.elastic.co/u/sgreszcz)\
**Post date:** [September 1, 2020, 1:40pm UTC](https://discuss.elastic.co/t/illegal-argument-exception-index-lifecycle-rollover-alias-does-not-point-to-index/247089/2 "2020-09-01T13:40:56Z")

</div>

Also a previous question: [Does ILM work in Logstash with custom index names?](https://discuss.elastic.co/t/does-ilm-work-in-logstash-with-custom-index-names/235816)

And the issue I raised as the ilm\_pattern =\> "000001" didn't work either:

```auto
output {
    elasticsearch{
    	hosts => "${ELASTICSEARCH_HOST}:${ELASTICSEARCH_PORT}"
    	index => "%{[@metadata][kafka][topic]}-%{+YYYY.MM.dd}"
# ilm_rollover_alias => "%{[@metadata][kafka][topic]}"
# ilm_policy => "%{[@metadata][kafka][topic]}"
    	ilm_pattern => "000001"
    }
}

```

I opened an issue here: [https://github.com/elastic/logstash/issues/12214](https://github.com/elastic/logstash/issues/12214)

I saw that @warkolm was addressing a similar question here: [How to correct custom logstash index name for use by ILM](https://discuss.elastic.co/t/how-to-correct-custom-logstash-index-name-for-use-by-ilm/246346)

---

_[View the full topic](https://discuss.elastic.co/t/illegal-argument-exception-index-lifecycle-rollover-alias-does-not-point-to-index/247089)._