# Conflit index template managed by fleet

**URL:** <https://discuss.elastic.co/t/conflit-index-template-managed-by-fleet/360360>\
**Category:** Elastic Agent\
**Tags:** fleet\
**Created:** [May 28, 2024, 9:10am UTC](https://discuss.elastic.co/t/conflit-index-template-managed-by-fleet/360360 "2024-05-28T09:10:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ahmed\_charafouddine](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ahmed_charafouddine/32/45129_2.png) [@ahmed\_charafouddine](https://discuss.elastic.co/u/ahmed_charafouddine)\
**Post date:** [May 28, 2024, 9:10am UTC](https://discuss.elastic.co/t/conflit-index-template-managed-by-fleet/360360/1 "2024-05-28T09:10:10Z")

</div>

Hello,

After upgrading our Elastic cluster from 8.11 to 8.13.4, we encountered an issue related to the index template. The followin error has appeared :

`illegal_argument_exception Root causes: illegal_argument_exception: index template [logs-tibco.fonctionnel] has index patterns [logs-tibco.fonctionnel-*] matching patterns from existing templates [logs-tibco.fonctionnel-ppr] with patterns (logs-tibco.fonctionnel-ppr => [logs-tibco.fonctionnel-ppr-*]) that have the same priority [200], multiple index templates may not match during index creation, please use a different priority`

This issue occurs when we try to update the custom log plugin. It is blocking us from creating new Custom Log Integration.

**Actions taken :**  
It appears that there is a priority conflit between the template `logs-tibco.fonctionnel` and `logs-tibco.fonctionnel-ppr` , both having prority of 200 and imilar patterns. The prevents the creation of indices matching the pattern`logs-tibco.fonctionnel-*`

Both of these indexe templates, as well as the custom logs associated with theses index templates, have been deleted. Despite this, **we still encounter this problem** when trying to create new custom logs or update the custom log plugin

Could anyone help me resolve this problem?

Thank you

---

<div class="post-metadata">

**Author:** ![jelmokri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jelmokri/32/135171_2.png) [@jelmokri](https://discuss.elastic.co/u/jelmokri)\
**Post date:** [June 10, 2024, 1:07pm UTC](https://discuss.elastic.co/t/conflit-index-template-managed-by-fleet/360360/2 "2024-06-10T13:07:42Z")

</div>

Hello, any news about it ?  
I have the same issue when upgrading to 8.14.0 and still on Custom logs integration upgrade.

Did you solve it ?

---

<div class="post-metadata">

**Author:** ![MarianBejan](https://avatars.discourse-cdn.com/v4/letter/m/c2a13f/32.png) [@MarianBejan](https://discuss.elastic.co/u/MarianBejan)\
**Post date:** [June 17, 2024, 11:53am UTC](https://discuss.elastic.co/t/conflit-index-template-managed-by-fleet/360360/3 "2024-06-17T11:53:13Z")

</div>

Having the same issue, on 8.13.2. Tried switching the priorities also, but with no success.

---

<div class="post-metadata">

**Author:** ![ahmed\_charafouddine](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ahmed_charafouddine/32/45129_2.png) [@ahmed\_charafouddine](https://discuss.elastic.co/u/ahmed_charafouddine)\
**Post date:** [October 25, 2024, 1:07pm UTC](https://discuss.elastic.co/t/conflit-index-template-managed-by-fleet/360360/4 "2024-10-25T13:07:01Z")

</div>

I solved it by deleting all custom log type integrations and then recreating them.