# ILM config for beats **URL:** \ **Category:** Beats\ **Created:** [September 9, 2019, 8:19am UTC](https://discuss.elastic.co/t/ilm-config-for-beats/198629 "2019-09-09T08:19:45Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![coudenysj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/coudenysj/32/23108_2.png) [@coudenysj](https://discuss.elastic.co/u/coudenysj)\ **Post date:** [September 9, 2019, 8:19am UTC](https://discuss.elastic.co/t/ilm-config-for-beats/198629/1 "2019-09-09T08:19:45Z")
Hi, I was wondering if the index logic for beats was changed due to ILM settings. In the logs of filebeat, I see `Set output.elasticsearch.index to 'filebeat-7.3.1' as ILM is enabled.`. This is different from the base config where the beats to to filebeat-7.3.1-YYYY-MM-DD. The problem is that the template patterns won't work anymore (because they are configured by default to listen to filebeat-7.3.1-\*). I want to fix the policies on my cluster, but I was wondering if the date suffix is still desired, now that we have ILM to rollover indices. What is the view of Elastic on this? ---
**Author:** ![coudenysj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/coudenysj/32/23108_2.png) [@coudenysj](https://discuss.elastic.co/u/coudenysj)\ **Post date:** [September 9, 2019, 9:39am UTC](https://discuss.elastic.co/t/ilm-config-for-beats/198629/2 "2019-09-09T09:39:27Z")
My aliases were broken on the server, so that problem is fixed, but the question still remains if it is still useful to use date suffixes on indices when using ILM. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 7, 2019, 11:39am UTC](https://discuss.elastic.co/t/ilm-config-for-beats/198629/3 "2019-10-07T11:39:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.