Timeout Purepath and more than one request inside shown in one purepath
Hello,
I have a situation that i can not understand clearly.There is an Login transaction talkes more than 800s. When I check the purepath of the request.
I see lots of login call inside the same purepath.
What i do not undestand is
-Why this requet not capured as a sepate purepath and shown in same purepath ? May it be broad force attach ? I also see "dangereous ..." exception
-This purepath last in timeout. and I see most of the time spent in IIS ( I/O ) so is this value trustful or I see it like that just because of purepath is timedout and
dt can not calculate the timings proporly. What is the general behaviour of dynatrace of timeout purepaths ?
See purepaths ;
Hi. This really is a very interesting PurePath. Due to the fact that you exported the data withour confidential information it is a little hard to really follow the path - but - assuming that these ProcesRequestNotificationHelper subnodes are all on different .aspx URLs and not all on loginUser.aspx made it seam like our agent is incorrectly merging these Paths together.
On the other side it seems like all these ProcessRequestNotfi... nodes are executed in the same Thread (enable the Thread Name column). This could mean that your application is confiugred with a lot of IIS Modules that IIS is executing one after the other for every request. This would actually be normal behavior. Still - I havent seen such an extensive PurePath like yours with that many ProcessRequestNOtification.. nodes.
Can you try to restart your application and capture more PurePaths? Maybe there was an instrumentation issue during your first attempt.
If this problem persists and you are sure that you should actually see different PurePaths for different URLs that you are executing I suggest to open a support ticket
