# Invalid composable template

**URL:** <https://discuss.elastic.co/t/invalid-composable-template/382223>\
**Category:** APM\
**Tags:** server\
**Created:** [September 25, 2025, 11:34am UTC](https://discuss.elastic.co/t/invalid-composable-template/382223 "2025-09-25T11:34:05Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ekta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ekta/32/55987_2.png) [@Ekta](https://discuss.elastic.co/u/Ekta)\
**Post date:** [September 25, 2025, 11:34am UTC](https://discuss.elastic.co/t/invalid-composable-template/382223/1 "2025-09-25T11:34:06Z")

</div>

Hi

We are using Elasticsearch - 8.18.1

kibana - 8.18.6

APM-server - 8.18.1 in linux server - 22.04

We have upgraded Elasticsearch,kibana and APM-server from 7.17.27 to 8.18.1 after some time we are getting below error

[ERROR][o.e.x.c.t.IndexTemplateRegistry] [TEST02] error adding index template [logs-apm.error@mappings] for [apm]  
java.lang.IllegalArgumentException: updating component template [logs-apm.error@mappings] results in invalid composable template [logs-apm.error] after templates are merged  
at org.elasticsearch.cluster.metadata.MetadataIndexTemplateService.addComponentTemplate(MetadataIndexTemplateService.java:350) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.metadata.MetadataIndexTemplateService$3.execute(MetadataIndexTemplateService.java:250) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.metadata.MetadataIndexTemplateService$1.executeTask(MetadataIndexTemplateService.java:150) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.metadata.MetadataIndexTemplateService$1.executeTask(MetadataIndexTemplateService.java:147) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.SimpleBatchedExecutor.execute(SimpleBatchedExecutor.java:71) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.service.MasterService.innerExecuteTasks(MasterService.java:1075) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:1038) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.service.MasterService.executeAndPublishBatch(MasterService.java:245) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.service.MasterService$BatchingTaskQueue$Processor.lambda$run$2(MasterService.java:1691) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.action.ActionListener.run(ActionListener.java:454) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.service.MasterService$BatchingTaskQueue$Processor.run(MasterService.java:1688) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.service.MasterService$5.lambda$doRun$0(MasterService.java:1283) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.action.ActionListener.run(ActionListener.java:454) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.cluster.service.MasterService$5.doRun(MasterService.java:1262) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:1044) ~[elasticsearch-8.18.1.jar:?]  
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:27) ~[elasticsearch-8.18.1.jar:?]  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]  
at java.lang.Thread.run(Thread.java:840) ~[?:?]  
Caused by: java.lang.IllegalArgumentException: composable template [logs-apm.error] template after composition with component templates [logs-apm.error@mappings, logs-apm.error@settings, logs-apm.error@custom, .fleet\_component\_template-1] is invalid

Can any help here what we can do over here?

---

<div class="post-metadata">

**Author:** ![marclop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marclop/32/119339_2.png) [@marclop](https://discuss.elastic.co/u/marclop)\
**Post date:** [September 29, 2025, 5:53am UTC](https://discuss.elastic.co/t/invalid-composable-template/382223/2 "2025-09-29T05:53:27Z")

</div>

Hi @Ekta ,

Are you using any extra component templates? It may be that the templates aren’t valid.

---

<div class="post-metadata">

**Author:** ![Ekta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ekta/32/55987_2.png) [@Ekta](https://discuss.elastic.co/u/Ekta)\
**Post date:** [October 1, 2025, 6:58am UTC](https://discuss.elastic.co/t/invalid-composable-template/382223/3 "2025-10-01T06:58:05Z")

</div>

When I get detail with below API GET \_index\_template/traces-apm I got below detail  
"template": {

```
      "settings": {

        "index": {

          "default_pipeline": "traces-apm-7.17.0"

        }

      },

```

but my apm-server version is 8.18.1 so what to do?

---

<div class="post-metadata">

**Author:** ![Ekta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ekta/32/55987_2.png) [@Ekta](https://discuss.elastic.co/u/Ekta)\
**Post date:** [October 6, 2025, 12:46pm UTC](https://discuss.elastic.co/t/invalid-composable-template/382223/4 "2025-10-06T12:46:07Z")

</div>

Hi

Is there any things is used to ingest pipeline manually for 8.18.1?

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 6, 2025, 2:40pm UTC](https://discuss.elastic.co/t/invalid-composable-template/382223/5 "2025-10-06T14:40:50Z")

</div>

Have you tried to simulate the teamplate

> **[Simulate multi-component templates | Elasticsearch Guide \[8.18\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.18/simulate-multi-component-templates.html)**

> [@Ekta](#):
>
> We are using Elasticsearch - 8.18.1
> 
> kibana - 8.18.6

Also Elastic and Kibana should be at the same version Kibana ahead of Elastic is not really a good thing.

It looks to me perhaps the upgrade of APM (and are you using the server binary of the APM Integration), perhaps did not complete.

---

<div class="post-metadata">

**Author:** ![Ekta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ekta/32/55987_2.png) [@Ekta](https://discuss.elastic.co/u/Ekta)\
**Post date:** [October 8, 2025, 6:21am UTC](https://discuss.elastic.co/t/invalid-composable-template/382223/6 "2025-10-08T06:21:21Z")

</div>

@stephenb we have upgrade apm-server from 7.17.20 to 8.18.1 using dpkg -i pkgname.deb, nothing extra we did over here

Is there any extra we need to do over here?

---

<div class="post-metadata">

**Author:** ![Ekta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ekta/32/55987_2.png) [@Ekta](https://discuss.elastic.co/u/Ekta)\
**Post date:** [October 16, 2025, 8:03am UTC](https://discuss.elastic.co/t/invalid-composable-template/382223/7 "2025-10-16T08:03:45Z")

</div>

Is there any how to reload templates in apm-server-8.18.1?

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 16, 2025, 2:01pm UTC](https://discuss.elastic.co/t/invalid-composable-template/382223/8 "2025-10-16T14:01:48Z")

</div>

Hi @Ekta

> **[APM Server command reference | Elastic Observability \[8.18\] | Elastic](https://www.elastic.co/guide/en/observability/8.18/apm-command-line-options.html)**

There used to be a direct command to reload but I don't see that. It looks like you can export them and then I guess you will need to manually put them in.

I'm not sure what state your system is, but if you removed them and restarted the APM server I would expect it would reload them.

But it looks like you can export them and take a look. You could then reload them by hand I suppose