# Central Management and Default ILM

**URL:** <https://discuss.elastic.co/t/central-management-and-default-ilm/206386>\
**Category:** Beats\
**Tags:** fleet, ilm-index-lifecycle-management\
**Created:** [November 4, 2019, 11:25am UTC](https://discuss.elastic.co/t/central-management-and-default-ilm/206386 "2019-11-04T11:25:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rverchere](https://avatars.discourse-cdn.com/v4/letter/r/dbc845/32.png) [@rverchere](https://discuss.elastic.co/u/rverchere)\
**Post date:** [November 4, 2019, 11:25am UTC](https://discuss.elastic.co/t/central-management-and-default-ilm/206386/1 "2019-11-04T11:25:30Z")

</div>

Hello,

I have a filebeat that uses the default ILM, creating indices like 'filebeat-7.4.1-2019.11.01-000001'.  
After enroll the filebeat to the Central Management, the default ILM is not taken in account, and filebeat creates new indices like 'filebeat-7.4.1-2019.11.02'.  
When setting the original config (unenroll), filebeat start to write to the correct index.

I know Beats Central Management does not manage ILM per beats agent, but how can I configure my beats agent to use the correct one then?

Thanks!

---

<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:** [December 2, 2019, 1:25pm UTC](https://discuss.elastic.co/t/central-management-and-default-ilm/206386/2 "2019-12-02T13:25:38Z")

</div>

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