Hi everyone,
For a customer we have a situation where we can see lots of latches waiting and a high average wait time in the metrics coming from the MSSQL extension (remote).
A trace that was executed specifically during the peak at 08:46 shows fast queries, but is still waiting a long time until the request is processed.
In the new tracing app, Dynatrace shows the message "Elapsed time from the start of the first span to the end of the last span."
In the distributed traces classic app is this long timing categorized as "Other".
We have identified that the database is a lot of latches waiting a long time on resources in general and that there is response time issues for queries caused by contention of shared resources within the SQL server.
My question is, could it be that Dynatrace sees these these long response times on the middelware as 'Other' timings, because the SQL server is waiting internally and the client waits on the SQL response, so the delay is not falling under any of these categories like CPU or network IO?
Featured Posts
