topic Re: Understanding Response times in PurePath in Open Q&A

Understanding Response times in PurePath

Malaik — Mon, 06 Jun 2022 09:08:57 GMT

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.

BRs,

Re: Understanding Response times in PurePath

Julius_Loman — Mon, 06 Jun 2022 09:29:20 GMT

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

Re: Understanding Response times in PurePath

Malaik — Mon, 06 Jun 2022 11:04:02 GMT

This is what I can observe:

Re: Understanding Response times in PurePath

AntonioSousa — Mon, 06 Jun 2022 11:42:11 GMT

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

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

Re: Understanding Response times in PurePath

Malaik — Mon, 06 Jun 2022 11:51:48 GMT

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?

Re: Understanding Response times in PurePath

AntonioSousa — Mon, 06 Jun 2022 14:32:10 GMT

@Malaik,

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...

Re: Understanding Response times in PurePath

theharithsa — Tue, 07 Jun 2022 02:19:52 GMT

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.

Re: Understanding Response times in PurePath

techean — Tue, 07 Jun 2022 03:22:18 GMT

Hey, this could be due to adaptive traffic control

Do check this related solution Solved: Re: Purepath - Dynatrace Community

And refer this documentation Errors of PurePath® capture | Dynatrace Docs

https://www.dynatrace.com/support/help/shortlink/purepath-capture-errors#consequences-of-missing-data