Server side response time and Client side response time in Dynatrace

shashank_b_agra — Tue, 04 Feb 2020 13:39:21 GMT

response time.pngHi, I am trying to find out the cause of slow response time of one of the API for my web application. I have tried to use Purepath and came across two attributes server-side response time and client-side response time. What does it mean from the screenshot attached. The flow is Apache -> Tomcat and I don't understand what is causing that 11.7 seconds of time? How do i find out if it's the Network issue?

Also what does that "other" time represent here as it is what taking the longest time?

@Dave M. @Joseph M. H. @Saravanan S. @Larry R.

Any help is appreciated.

Re: Server side response time and Client side response time in Dynatrace

justin_hogue — Mon, 16 Oct 2023 14:31:49 GMT

Hello,

I'm unable to pinpoint whether this is a network issue, but I can try to answer some of your other questions. I believe that server-side response time is calculated based on how much time was spent in that particular service as well as any downward services it may have called. Client-side response time is being calculated based on the perspective of the caller, so beginning with when the client called the service and up until that service finishes executing and returns a value to the client service. For "Other" I believe the calculation is as follows:

Other = Total time - CPU - Wait - Sync - Suspension

Here are 2 posts that might help provide more detail:

https://community.dynatrace.com/questions/199674/what-is-service-client-side-response-time.html

https://community.dynatrace.com/questions/193685/what-does-other-time-mean-in-dynatrace.html?childToView=193686#answer-193686

Hope this helps!

topic Re: Server side response time and Client side response time in Dynatrace in Real User Monitoring

Server side response time and Client side response time in Dynatrace

Re: Server side response time and Client side response time in Dynatrace