# Filebeat elasticsearch output index setting breaking change? **URL:** \ **Category:** Beats\ **Tags:** ilm-index-lifecycle-management, filebeat\ **Created:** [April 5, 2022, 8:04pm UTC](https://discuss.elastic.co/t/filebeat-elasticsearch-output-index-setting-breaking-change/301667 "2022-04-05T20:04:51Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [April 5, 2022, 8:04pm UTC](https://discuss.elastic.co/t/filebeat-elasticsearch-output-index-setting-breaking-change/301667/1 "2022-04-05T20:04:51Z")
In prior filebeat doc (at least in 7.5.0) the output index section stated: > The index setting is ignored when index lifecycle management is enabled. If you’re sending events to a cluster that supports index lifecycle management, see Configure index lifecycle management to learn how to change the index name. This appears to have been true thru 7.17, but in 8.1.2, the name of the ilm.rollover\_alias doesn't seem to be used for output, it reverted to the default ILM filebeat index name. The 8.1 doc still has the forward reference to [_Index lifecycle management (ILM)_](https://www.elastic.co/guide/en/beats/filebeat/8.1/ilm.html) but that part no longer says it will change the output index name. It appears I now will have to put the index: name in all output sections. Has anyone else noticed this? Did I miss it in breaking changes? There are SO MANY release notes to read, I can't keep up. Thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 3, 2022, 10:05pm UTC](https://discuss.elastic.co/t/filebeat-elasticsearch-output-index-setting-breaking-change/301667/2 "2022-05-03T22:05:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.