# Custom ILM policies for APM DataStreams **URL:** \ **Category:** Elastic Observability\ **Created:** [March 18, 2024, 1:56am UTC](https://discuss.elastic.co/t/custom-ilm-policies-for-apm-datastreams/355568 "2024-03-18T01:56:15Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![rpanand24](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rpanand24/32/132713_2.png) [@rpanand24](https://discuss.elastic.co/u/rpanand24)\ **Post date:** [March 18, 2024, 3:12am UTC](https://discuss.elastic.co/t/custom-ilm-policies-for-apm-datastreams/355568/8 "2024-03-18T03:12:48Z")
I have the similar requirement for logs and metrics also. But this is too much of over head maintenance for the APM functionality users. I believe most of the enterprises will have a similar requirement to manage data per environment differently (I see another post here [Indexing Application Trace Data into Separate Indices Based on Application Names - Elastic Observability / APM - Discuss the Elastic Stack](https://discuss.elastic.co/t/indexing-application-trace-data-into-separate-indices-based-on-application-names/353437)). So is there any other way to achieve this (may be future release) ? I am thinking about allowing variable configuration in component templates like below. And parse and apply the data from the first data stream creation. Its is good to have the apm templates as managed instead of cloning and maintaining. ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/f/ffbd1eb6c012239ed7de1405473f6cf94fdf90da.png) --- _[View the full topic](https://discuss.elastic.co/t/custom-ilm-policies-for-apm-datastreams/355568)._