# APM Integration Issue: Failed to Index traces After Upgrade from 8.12.1 to 8.15.1

**URL:** <https://discuss.elastic.co/t/apm-integration-issue-failed-to-index-traces-after-upgrade-from-8-12-1-to-8-15-1/367032>\
**Category:** APM\
**Tags:** ilm-index-lifecycle-management, server\
**Created:** [September 24, 2024, 11:00am UTC](https://discuss.elastic.co/t/apm-integration-issue-failed-to-index-traces-after-upgrade-from-8-12-1-to-8-15-1/367032 "2024-09-24T11:00:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SachinJoshi](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@SachinJoshi](https://discuss.elastic.co/u/SachinJoshi)\
**Post date:** [September 24, 2024, 11:00am UTC](https://discuss.elastic.co/t/apm-integration-issue-failed-to-index-traces-after-upgrade-from-8-12-1-to-8-15-1/367032/1 "2024-09-24T11:00:22Z")

</div>

We did elastic upgrade from 8.12.1 to 8.15.1, Following things upgrade and all have same version right now which is 8.15.1.

Elastic Data node  
Kibana  
Apm Server  
Fleets  
Beats

after upgrade apm does not have any data and when we check the log following error we got it.

```auto
 APM Server v8.15.1, which is newer than the installed APM integration (v8.12.2-preview-1707233477). The APM integration must be upgraded.","service.name":"apm-server","documents":1,"ecs.version":"1.6.0"}

```

we checked the ingest pipeline and there is still old pipeline there which is trace-apm-8.12.1, i should be upgraded to 8.15.1 but it did not.

I created new pipeline with name 8.15.1 but it does not work getting same error.

What i have to do here ? Should i reinstalled APM integration so it will created new pipeline or updated existing pipeline ?

---

<div class="post-metadata">

**Author:** ![Kostya\_Masliuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kostya_masliuk/32/137867_2.png) [@Kostya\_Masliuk](https://discuss.elastic.co/u/Kostya_Masliuk)\
**Post date:** [September 25, 2024, 10:25pm UTC](https://discuss.elastic.co/t/apm-integration-issue-failed-to-index-traces-after-upgrade-from-8-12-1-to-8-15-1/367032/2 "2024-09-25T22:25:43Z")

</div>

Hello @SachinJoshi, we are tracking a similar issue when updating to APM Server v8.15.1 from APM Server v8.12.1. The current workaround is to manually rollover the relevant data streams by running the following requests (assuming the default namespace).

```auto
POST /traces-apm-default/_rollover
POST /traces-apm.rum-default/_rollover
POST /logs-apm.error-default/_rollover
POST /logs-apm.app-default/_rollover
POST /metrics-apm.app-default/_rollover
POST /metrics-apm.internal-default/_rollover
POST /metrics-apm.service_destination.1m-default/_rollover
POST /metrics-apm.service_destination.10m-default/_rollover
POST /metrics-apm.service_destination.60m-default/_rollover
POST /metrics-apm.service_summary.1m-default/_rollover
POST /metrics-apm.service_summary.10m-default/_rollover
POST /metrics-apm.service_summary.60m-default/_rollover
POST /metrics-apm.service_transaction.1m-default/_rollover
POST /metrics-apm.service_transaction.10m-default/_rollover
POST /metrics-apm.service_transaction.60m-default/_rollover
POST /metrics-apm.transaction.1m-default/_rollover
POST /metrics-apm.transaction.10m-default/_rollover
POST /metrics-apm.transaction.60m-default/_rollover

```