cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Why am I getting corrupted PurePaths after a migration from 6.x to 7.0?

Dynatrace 7.0 shows PurePaths as corrupt. These PurePaths were not visible in 6.x.

The PurePaths details show the following text:

PurePath Details
State: Unable to determine PurePath success because of the following reasons:
Path Corrupted: The PurePath was created from a sub-path
which could not be linked to any parent path

Why is that?

4 REPLIES 4

Dynatrace 7.0 contains a new feature, internally called "lost+found" transactions.

Sub-paths that cannot be linked to a root path are displayed and marked as corrupt. In earlier versions, these PurePaths would not show up but were ignored by the server.

Due to the new feature, these lost+found transactions are now visible in 7.0 in addition to any transactions that both 6.x and 7.0 would show.

rohith_samudral
Organizer

Hey Markus B, Could you please help me understand the purpose of the "lost+found" transactions. I have just migrated and i am seeing the same thing. How do we use this new information.

sebastien_paque
Newcomer

Hi , so how should we react about this ? I see an incident talking about >=1000 corrupted Purepaths detected . How can we fix those ?? or should I open a support ticket ?

jcamps
Advisor

Hi all,

I'm in the same situation and my customer, how do we use this new information?

Regards!