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

Understanding Response times in PurePath

DynaMight Pro
DynaMight Pro

Hi Guys,


Let talk about Purepaths (traces)


In the bellow example



The PurePaths Response time is 2.5 min.

The database Request is 30sec.


I see 

Execution breakdown around 80 % Other.
And a big blank space between 2 queries (the grey line): why its not sequentiel? (Database lock?)
How can I explain everything and Where the time is spent other than the 30sec in the query.


thanks to whoever is going to comment.


Sharing Knowledge

DynaMight Guru
DynaMight Guru

Examine method hotspots on the ASP.NET node for this PurePath and the code level tab information.

Certified Dynatrace Master | Alanata a.s., Slovakia, Dynatrace Master Partner

This is what I can observe:










Sharing Knowledge

Sorry, clicked "Accept as solution" instead of "Reply".

@Malaik, was this observed during a recycle/restart of an app pool?

Antonio Sousa

Thanks @AntonioSousa 


I just discover this kind of purepaths after navigating in Problems.


But I can see this  in the root cause section in the problem



So, what is the relation between all those elements?


Sharing Knowledge


See that you are using OutSystems 😁

When it crashes, the app pool has to be restarted, and the restart has to do a lot of things. All requests that come in during that phase will get locking, due namely to .Net compilations and other restarting needs...

Antonio Sousa

Dynatrace Champion
Dynatrace Champion

Hi @Malaik 
I have observed this in many customer places who are using ASP.NET. It is an expected behaviour from Dynatrace. Dynatrace works in such a way that it captures the details of the most important methods that are under execution and not every method the program executes will be captured in PurePaths - This is because to reduce the overhead on the application by OneAgent and deep monitoring. In order to look at this, what you can do is to create custom service for those methods and capture the details on what is happening. 

As per the screenshot, the timing data is around 70% is spent on other that means that time which the request has took is unmonitored by Dynatrace or Dynatrace is not able to detect what that timing is. It just shows other as the result of the remaining of final response time of the request. 

Love more, hate less; Technology for all, together we grow.

Dynatrace Champion
Dynatrace Champion