# Elastic 7.10.2: no way to automatically create the first index. Manually kickstart ILM still mandatory?

**URL:** <https://discuss.elastic.co/t/elastic-7-10-2-no-way-to-automatically-create-the-first-index-manually-kickstart-ilm-still-mandatory/266811>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [March 10, 2021, 1:28pm UTC](https://discuss.elastic.co/t/elastic-7-10-2-no-way-to-automatically-create-the-first-index-manually-kickstart-ilm-still-mandatory/266811 "2021-03-10T13:28:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ORich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/orich/32/21675_2.png) [@ORich](https://discuss.elastic.co/u/ORich)\
**Post date:** [March 10, 2021, 1:28pm UTC](https://discuss.elastic.co/t/elastic-7-10-2-no-way-to-automatically-create-the-first-index-manually-kickstart-ilm-still-mandatory/266811/1 "2021-03-10T13:28:25Z")

</div>

Dear experts,  
I am running Elastic 7.10.2. I would like to manage a first index with syntax filebeat-7.10.2-postfix-2021.03.10-000001. Thanks to ILM rollover mechanism next one would be filebeat-7.10.2-postfix-2021.03.10-000002 ...

Unfortunately, the first created index name is filebeat-7.10.2-postfix .... as it should be the alias name instead. I thought it was not needed anymore to kickstart ILM, by manually creating the first index in version 7.10.2 ?

All your support and inputs highly appreciated.

Here is my filebeat configuration extract:

```auto
setup.ilm.enabled: true
setup.ilm.rollover_alias: 'filebeat-%{[agent.version]}-postfix'
setup.ilm.pattern: "{now/d{yyyy.MM.dd}}-000001"
setup.ilm.policy_name: "datastream_policy_30d"
setup.ilm.check_exists: true
setup.ilm.overwrite: false

```

Here are the filebeat log outputs regarding ILM:

```auto
2021-03-10T14:06:50.898+0100 INFO [index-management] idxmgmt/std.go:261 Auto ILM enable success.
2021-03-10T14:06:50.900+0100 INFO [index-management.ilm] ilm/std.go:139 do not generate ilm policy: exists=true, overwrite=false
2021-03-10T14:06:50.900+0100 INFO [index-management] idxmgmt/std.go:274 ILM policy successfully loaded.
2021-03-10T14:06:50.900+0100 INFO [index-management] idxmgmt/std.go:407 Set setup.template.name to '{filebeat-7.10.2-postfix {now/d{yyyy.MM.dd}}-000001}' as ILM is enabled.
2021-03-10T14:06:50.900+0100 INFO [index-management] idxmgmt/std.go:412 Set setup.template.pattern to 'filebeat-7.10.2-postfix-*' as ILM is enabled.
2021-03-10T14:06:50.900+0100 INFO [index-management] idxmgmt/std.go:446 Set settings.index.lifecycle.rollover_alias in template to {filebeat-7.10.2-postfix {now/d{yyyy.MM.dd}}-000001} as ILM is enabled.
2021-03-10T14:06:50.900+0100 INFO [index-management] idxmgmt/std.go:450 Set settings.index.lifecycle.name in template to {datastream_policy_30d {"policy":{"phases":{"hot":{"actions":{"rollover":{"max_age":"30d","max_size":"50gb"}}}}}}} as ILM is enabled.
2021-03-10T14:06:52.418+0100 INFO template/load.go:117 Try loading template filebeat-7.10.2-postfix to Elasticsearch
2021-03-10T14:06:52.582+0100 INFO template/load.go:109 template with name 'filebeat-7.10.2-postfix' loaded.
2021-03-10T14:06:52.582+0100 INFO [index-management] idxmgmt/std.go:298 Loaded index template.
2021-03-10T14:06:52.616+0100 INFO [index-management] idxmgmt/std.go:307 Write alias exists already
2021-03-10T14:06:52.616+0100 INFO [publisher_pipeline_output] pipeline/output.go:151 Connection to backoff(elasticsearch(http://elasticsearch.service.webcom:9200)) established

```

---

<div class="post-metadata">

**Author:** ![ORich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/orich/32/21675_2.png) [@ORich](https://discuss.elastic.co/u/ORich)\
**Post date:** [March 11, 2021, 8:30am UTC](https://discuss.elastic.co/t/elastic-7-10-2-no-way-to-automatically-create-the-first-index-manually-kickstart-ilm-still-mandatory/266811/2 "2021-03-11T08:30:21Z")

</div>

I updated setup.ilm.rollover\_alias with value 'fbeat-%{[agent.version]}-postfix' in order to avoid an extra matching with the default filebeat legacy template  
Then, fbeat-7.10.2-postfix-2021.03.10-000001is automatically kickstarted

---

<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 8, 2021, 8:30am UTC](https://discuss.elastic.co/t/elastic-7-10-2-no-way-to-automatically-create-the-first-index-manually-kickstart-ilm-still-mandatory/266811/3 "2021-04-08T08:30:59Z")

</div>

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