# APM The selected trace cannot be found after 7.17.1 -\> 8.1 upgrade

**URL:** <https://discuss.elastic.co/t/apm-the-selected-trace-cannot-be-found-after-7-17-1-8-1-upgrade/299964>\
**Category:** APM\
**Tags:** docker, fleet, python, server, elastic-agent\
**Created:** [March 17, 2022, 3:12pm UTC](https://discuss.elastic.co/t/apm-the-selected-trace-cannot-be-found-after-7-17-1-8-1-upgrade/299964 "2022-03-17T15:12:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![edwardcccc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/edwardcccc/32/103161_2.png) [@edwardcccc](https://discuss.elastic.co/u/edwardcccc)\
**Post date:** [March 17, 2022, 3:12pm UTC](https://discuss.elastic.co/t/apm-the-selected-trace-cannot-be-found-after-7-17-1-8-1-upgrade/299964/1 "2022-03-17T15:12:54Z")

</div>

If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text 🙂

**Kibana version** :  
Docker 8.1.0

**Elasticsearch version** :  
Docker 8.1.0

**APM Server version** :  
Elastic Agent Fleet Server 8.1.0

**APM Agent language and version** :  
Python Flask 6.8.1

**Browser version** :  
Chrome 99

I have an existing installation of  
Docker  
Elasticsearch 7.17.1  
Kibana 7.17.1  
APM Server 7.17.1

I upgraded to 8.1.0 using  
Docker  
Elasticsearch 8.1.0 ([docker.elastic.co/elasticsearch/elasticsearch:8.1.0](http://docker.elastic.co/elasticsearch/elasticsearch:8.1.0))  
Kibana 8.1.0 ([docker.elastic.co/kibana/kibana:8.1.0](http://docker.elastic.co/kibana/kibana:8.1.0))  
APM Server 8.1.0 ([docker.elastic.co/apm/apm-server:8.1.0](http://docker.elastic.co/apm/apm-server:8.1.0))  
Then I changed to use elastic agent with fleet server to swap out the above container  
[docker.elastic.co/beats/elastic-agent:8.1.0](http://docker.elastic.co/beats/elastic-agent:8.1.0)

apm events goes to Elasticsearch and shows up on the dashboard no problem

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/2/723fccae59bec24133c78ddaecbfc9d001a33aea.png)  
However, I cannot see the trace  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/e/1e37177f8c013df39b8d79e05d0f02add18adaae.png)  
I am able to see trace in the document  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/1/51a87d21c35b136eed663769f9be6bbed7e0933d.png)

I can still see trace from earlier times which is ingested in 7.17.1

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/3/c39269209f4ae3af6275e228c19cf566157c01eb.png)

clicking on these two links doesnot show anything

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/b/4be1ffc7e7b1be8af02b02fc9744607f7cacb195.png)

I have tried to uninstall APM integration, remove assets using this button and reinstall apm integration, still has the problem

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/c/bcf59200669443304b7782b29c0a52214afb1d75.png)

---

<div class="post-metadata">

**Author:** ![swchandu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swchandu/32/95295_2.png) [@swchandu](https://discuss.elastic.co/u/swchandu)\
**Post date:** [March 18, 2022, 1:08pm UTC](https://discuss.elastic.co/t/apm-the-selected-trace-cannot-be-found-after-7-17-1-8-1-upgrade/299964/2 "2022-03-18T13:08:54Z")

</div>

> [@edwardcccc](#):
>
> install APM integration, remove assets using this button and reinstall apm integration, still has the problem

I was also facing the same issue after 8.0 upgrade. I have noticed a mapping error in the fleet-apm server logs. so, deleted apm related indexes and also datastreams(doubting this too). Re-integrated apm and able to get the traces.  
I haven't done in-depth analysis as env is dev. Thanks for posting it.

---

<div class="post-metadata">

**Author:** ![stuart.nelson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stuart.nelson/32/99866_2.png) [@stuart.nelson](https://discuss.elastic.co/u/stuart.nelson)\
**Post date:** [March 21, 2022, 2:46pm UTC](https://discuss.elastic.co/t/apm-the-selected-trace-cannot-be-found-after-7-17-1-8-1-upgrade/299964/3 "2022-03-21T14:46:16Z")

</div>

Can you share your index templates, and check the server logs to see if there's a mapping error, like what @swchandu saw when they upgraded?

---

<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:** [April 11, 2022, 10:46am UTC](https://discuss.elastic.co/t/apm-the-selected-trace-cannot-be-found-after-7-17-1-8-1-upgrade/299964/4 "2022-04-11T10:46:27Z")

</div>

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