topic Distributed trace duration doesn't add up in Open Q&A

Distributed trace duration doesn't add up

garytmui — Wed, 03 Apr 2024 09:51:33 GMT

I'm trying to understand why my IIS / .NET request response time is taking so long. In this case, it reflects 22.2s response time and duration, but the elapsed time of the last call (UpdateRequestCache) does not reflect 22+ seconds. Is there a way to tell where the 22s is taking place? Before or after the code execution?

Thanks!

Gary

Re: Distributed trace Duration doesn't add up

PacoPorro — Wed, 03 Apr 2024 07:40:09 GMT

Hi.
In the top right (3 dots ...) , you can use response time hotspots and method hotspots.

Re: Distributed trace Duration doesn't add up

Malaik — Wed, 03 Apr 2024 08:09:09 GMT

I have another question here

What a refine is doing exactly?

Re: Distributed trace Duration doesn't add up

garytmui — Wed, 03 Apr 2024 12:42:00 GMT

Thanks for the reply. I tried Response time hotspots and it showed me this but I'm not sure how to get to dig further. I see it attributes it to UrlRoutingModule which makes sense as this is a WebApi application, but it's still odd that almost all of the Duration of 22 seconds isn't within the Controller code seen being executed in the "Code" page. The duration of items in the Code page make up less than a second but can't tell where the rest of time is taken.

Does Dynatrace have any visibility into what happens before and after what is invoked in the Controller and seen in the Code level analysis?

Re: Distributed trace Duration doesn't add up

PacoPorro — Wed, 03 Apr 2024 12:48:24 GMT

click on the View method hotspots and check it.