28 Jan 2025 01:27 PM
Hello dear community,
I’m not sure if you’ve encountered this problem before. In some endpoints, I’m experiencing downtime where the database query clearly takes 8 seconds, but the getconsulta API keeps doing something until the 22nd second. That means, from second 8 to second 22, it seems like it’s working on the response.
This happens when there’s heavy load. Normally, this API responds in less than a second, but I have cases where it far exceeds this time, and I don’t know where to start troubleshooting.
Do you have any ideas or suggestions on how I can debug why it’s taking so long to respond?
28 Jan 2025 10:55 PM
Hey @Ellery
Looks like the nodejs process is taking a long time to process and make use of the database response. You should be able to find more detailed timings (assuming it has been captured) when you select the nodejs span in that trace. There is the timings and code level tab which should supply some information about what is going on in the process. This is just an example using a different trace.
There are other options such as looking at the method hotspots to get Dynatrace to do some of the analysis. Also you could go to the offending service and use the multidimensional analysis to look at what timings spike across all traces during the offending periods.
Hopefully some of these help get you closer!