# ILM settings not working **URL:** \ **Category:** Beats\ **Tags:** elastic-stack-monitoring, filebeat\ **Created:** [July 11, 2019, 3:38pm UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060 "2019-07-11T15:38:57Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![syedsfayaz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syedsfayaz/32/46657_2.png) [@syedsfayaz](https://discuss.elastic.co/u/syedsfayaz)\ **Post date:** [July 11, 2019, 3:38pm UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060/1 "2019-07-11T15:38:57Z")
Hi I am using filebeat and metric beat 7.2 and installing them on different windows and linux server. I want my beat agent to use existing ILM setting on elasticsearch but its overwriting it every time it is installed on new server. Below is my configuration. Looks like this is not working. setup.ilm.enabled: auto ``` # Configure the ILM write alias name. setup.ilm.rollover_alias: "metricbeat" # Configure rollover index pattern. setup.ilm.pattern: "{now/d}-000001" setup.ilm.check_exists: true setup.ilm.overwrite: false ``` ---
**Author:** ![Michal\_Pristas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michal_pristas/32/46639_2.png) [@Michal\_Pristas](https://discuss.elastic.co/u/Michal_Pristas)\ **Post date:** [July 15, 2019, 12:00pm UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060/2 "2019-07-15T12:00:26Z")
hey @syedsfayaz so ILM policies are overwritten every time new beat is installed right? is calling `filebeat setup --ilm-policy` part of your install script/procedure? How does your beat ES output configuration looks like? ---
**Author:** ![syedsfayaz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syedsfayaz/32/46657_2.png) [@syedsfayaz](https://discuss.elastic.co/u/syedsfayaz)\ **Post date:** [July 15, 2019, 3:11pm UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060/3 "2019-07-15T15:11:57Z")
This is the command I am using part of install script for both windows and linux. I am seeing same issue with metric,filebeat. `filebeat setup -e` `.\filebeat.exe setup` Can you tell me what exactly you are looking for when you say ES output configuration. ---
**Author:** ![Michal\_Pristas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michal_pristas/32/46639_2.png) [@Michal\_Pristas](https://discuss.elastic.co/u/Michal_Pristas)\ **Post date:** [July 15, 2019, 3:13pm UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060/4 "2019-07-15T15:13:25Z")
each beat is configured with an output such as `output.elasticsearch` I was curious to see this section (redacted of sensitive data) ---
**Author:** ![syedsfayaz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syedsfayaz/32/46657_2.png) [@syedsfayaz](https://discuss.elastic.co/u/syedsfayaz)\ **Post date:** [July 15, 2019, 3:33pm UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060/5 "2019-07-15T15:33:51Z")
``` output.elasticsearch: # Array of hosts to connect to. hosts: ["monitor.example.com:9200"] # Optional protocol and basic auth credentials. #protocol: "https" username: "elastic" password: " *******" ``` ---
**Author:** ![Michal\_Pristas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michal_pristas/32/46639_2.png) [@Michal\_Pristas](https://discuss.elastic.co/u/Michal_Pristas)\ **Post date:** [July 16, 2019, 9:10am UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060/6 "2019-07-16T09:10:55Z")
Can you skim the beat logs for ILM mentions. I assume you're not running OSS version of ES and ILM is available and enabled. ---
**Author:** ![syedsfayaz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syedsfayaz/32/46657_2.png) [@syedsfayaz](https://discuss.elastic.co/u/syedsfayaz)\ **Post date:** [July 16, 2019, 3:49pm UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060/7 "2019-07-16T15:49:53Z")
I see this in logs which should not be done as we have mentioned in the config not to overwrite if a template exists. Existing template will be overwritten, as overwrite is enabled. I did not get this "I assume you're not running OSS version of ES and ILM is available and enabled." but as per my understanding the ES I am running is from a tar file. ` ``` 2019-07-16T06:31:02.736-0700 INFO instance/beat.go:292 Setup Beat: metricbeat; Version: 7.2.0 2019-07-16T06:31:02.736-0700 INFO [index-management] idxmgmt/std.go:178 Set output.elasticsearch.index to 'metricbeat' as ILM is enabled. 2019-07-16T06:31:02.737-0700 INFO elasticsearch/client.go:166 Elasticsearch url: http://monitor.example.com:9200 2019-07-16T06:31:02.737-0700 INFO [publisher] pipeline/module.go:97 Beat name: rp.example.com 2019-07-16T06:31:02.737-0700 INFO elasticsearch/client.go:166 Elasticsearch url: http://monitor.example.com:9200 2019-07-16T06:31:02.743-0700 INFO elasticsearch/client.go:735 Attempting to connect to Elasticsearch version 7.2.0 2019-07-16T06:31:02.849-0700 INFO [index-management] idxmgmt/std.go:252 Auto ILM enable success. 2019-07-16T06:31:02.893-0700 INFO [index-management] idxmgmt/std.go:265 ILM policy successfully loaded. 2019-07-16T06:31:02.893-0700 INFO [index-management] idxmgmt/std.go:394 Set setup.template.name to '{metricbeat {now/d}-000001}' as ILM is enabled. 2019-07-16T06:31:02.893-0700 INFO [index-management] idxmgmt/std.go:399 Set setup.template.pattern to 'metricbeat-*' as ILM is enabled. 2019-07-16T06:31:02.893-0700 INFO [index-management] idxmgmt/std.go:433 Set settings.index.lifecycle.rollover_alias in template to {metricbeat {now/d}-000001} as ILM is enabled. 2019-07-16T06:31:02.893-0700 INFO [index-management] idxmgmt/std.go:437 Set settings.index.lifecycle.name in template to {metricbeat-7.2.0 {"policy":{"phases":{"hot":{"actions":{"rollover":{"max_age":"30d","max_size":"50gb"}}}}}}} as ILM is enabled. 2019-07-16T06:31:02.899-0700 INFO template/load.go:169 Existing template will be overwritten, as overwrite is enabled. 2019-07-16T06:31:03.065-0700 INFO template/load.go:108 Try loading template metricbeat to Elasticsearch 2019-07-16T06:31:03.146-0700 INFO template/load.go:100 template with name 'metricbeat' loaded. 2019-07-16T06:31:03.146-0700 INFO [index-management] idxmgmt/std.go:289 Loaded index template. 2019-07-16T06:31:03.147-0700 INFO [index-management] idxmgmt/std.go:300 Write alias successfully generated. Index setup finished. ``` ---
**Author:** ![syedsfayaz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syedsfayaz/32/46657_2.png) [@syedsfayaz](https://discuss.elastic.co/u/syedsfayaz)\ **Post date:** [July 24, 2019, 5:19am UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060/8 "2019-07-24T05:19:44Z")
@Michal_Pristas Hi Michal any idea why its not working? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 21, 2019, 5:19am UTC](https://discuss.elastic.co/t/ilm-settings-not-working/190060/9 "2019-08-21T05:19:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.