# ILM policies for multiple auto-generated indexes

**URL:** <https://discuss.elastic.co/t/ilm-policies-for-multiple-auto-generated-indexes/299732>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [March 15, 2022, 1:00pm UTC](https://discuss.elastic.co/t/ilm-policies-for-multiple-auto-generated-indexes/299732 "2022-03-15T13:00:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sam7](https://avatars.discourse-cdn.com/v4/letter/s/bc8723/32.png) [@sam7](https://discuss.elastic.co/u/sam7)\
**Post date:** [March 15, 2022, 1:00pm UTC](https://discuss.elastic.co/t/ilm-policies-for-multiple-auto-generated-indexes/299732/1 "2022-03-15T13:00:07Z")

</div>

Hi Team,

I have a logstash which is sending data streams to indexes created automatically in the process over Elasticsearch.

We have configured Logstash output section with index configuration as `index => "applogs-%{[fields][TEAM_ID]}-000001"` and routing data to respective teams.

I created ILM policy and Templates. But facing issue while creating alias as the index will follow the pattern like:  
applogs-team1-000001  
applogs-team2-000001  
.  
.  
applogs-team100-000001.

Please advise how we can plan the ILM rollout in such scenarios.

---

<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 12, 2022, 1:00pm UTC](https://discuss.elastic.co/t/ilm-policies-for-multiple-auto-generated-indexes/299732/2 "2022-04-12T13:00:58Z")

</div>

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