# Editing a managed policy can break Kibana

**URL:** <https://discuss.elastic.co/t/editing-a-managed-policy-can-break-kibana/347828>\
**Category:** Elasticsearch\
**Created:** [November 23, 2023, 8:40am UTC](https://discuss.elastic.co/t/editing-a-managed-policy-can-break-kibana/347828 "2023-11-23T08:40:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![DaddyYusk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daddyyusk/32/127617_2.png) [@DaddyYusk](https://discuss.elastic.co/u/DaddyYusk)\
**Post date:** [November 23, 2023, 8:40am UTC](https://discuss.elastic.co/t/editing-a-managed-policy-can-break-kibana/347828/1 "2023-11-23T08:40:59Z")

</div>

Hi,  
After a successful Fleet Server and Elastic Agent deployment, I wanted to tweak the ILM called "logs" and "metrics" which are both "Managed".

But when trying to do so, I encounter this well known warning :  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/a/5a7140691ec3437bcae83e4da223ca000011857f.png)

So after some research, I've found this great [post](https://discuss.elastic.co/t/use-of-customized-managed-ilm-policies/327594), where @leandrojmp suggest to follow this [tutorial](https://www.elastic.co/guide/en/fleet/current/data-streams-ilm-tutorial.html#data-streams-ilm-one).

This tutorial is great and perfectly clear, but wait... what if I want to apply the `90-days-default` ILM policy to ALL the `logs-*` and `metrics-*` datasets (and not for each one)?

Because this could be quite overwhelming and mostly if you have multiple namespaces...

Thanks a lot for your help.  
Regards.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [November 23, 2023, 12:11pm UTC](https://discuss.elastic.co/t/editing-a-managed-policy-can-break-kibana/347828/2 "2023-11-23T12:11:19Z")

</div>

> [@DaddyYusk](#):
>
> This tutorial is great and perfectly clear, but wait... what if I want to apply the `90-days-default` ILM policy to ALL the `logs-*` and `metrics-*` datasets (and not for each one)?

Not sure you can do that, the easiest way is to edit the built-in policies.

You will receive that warning, but you still can edit, this is what I did to add a delete phase to the `logs-*` lifecycle policy.

Until elastic fixes this and makes it easier to customize lifecycle policies, pipelines and mappings, there is not much else you can do.

---

<div class="post-metadata">

**Author:** ![DaddyYusk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daddyyusk/32/127617_2.png) [@DaddyYusk](https://discuss.elastic.co/u/DaddyYusk)\
**Post date:** [November 23, 2023, 1:19pm UTC](https://discuss.elastic.co/t/editing-a-managed-policy-can-break-kibana/347828/3 "2023-11-23T13:19:57Z")

</div>

Once again many thanks @leandrojmp for your answer!

Have a great day!  
Regards.

---

<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 21, 2023, 1:20pm UTC](https://discuss.elastic.co/t/editing-a-managed-policy-can-break-kibana/347828/4 "2023-12-21T13:20:29Z")

</div>

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