On the last Load Test we made (using Blazemeter) Dynatrace grouped purepaths that have nothing to do with each other under a single purepath.
This resulted in several corrupted purepaths with more than 10000 nodes.
I think this is due to the x-dynatrace tag, but I am not sure, can anyone shed some light?
All these "ProcessRequestNotificationHelper" should be new purepaths.
Third request (That should be a new purepath)
I'm attaching some purepaths, I think we are probably doing tagging wrong.
If you really believe that these PurePaths are supposed to be independent requests then it might be better to open a support ticket. I dont know your app - nor do I know your load test.
I've seen PurePaths like yours in the past though. PurePaths where ASP.NET is internally forwarding the request to other URLs so that other handlers get executed in the context of the initial request.In order to really know for sure I suggest to open a ticket as suggested earlier