What happened to "Client Time" in dynaTrace 5.6?
Hello,
I was running dT 5.0 and just upgraded to 5.6. In the Visits and User Action PurePath dashlets, I notice that there is no longer a column for client time or client contribution. Is there a way for me to get this back? If its no longer available, what's the reasoning behind why it was taken out? Without this metric, how else can we determine how much time was spent on the client-side?
Hi Klaus, I don't want to post the session on the forum since the session may contain personally identifiable information. Is there an email address I can send the session to instead? Or I can open a ticket with dT for further analysis.
Hi Andreas, I have a related question regarding User Action PurePaths.
I have a User Action, which on the User Action PurePath dashlet, lists the following response times:
Response Time = 21508 ms
Server Contribution = 2861 ms
Network Contribution = 18647 ms
However, in the Method pane below, where it shows the breakdown of the User Action PurePath, you can clearly see that most of the response time is on the server side, not the network side. I mean if you add up the server-time for all these sub-requests, you'll get around 18 seconds of server time. Why does dT show this 18 seconds as network time in the top pane, but in the lower pane, you can clearly see that its server-time. See attachment.
Hi Melanie,
Do you have a session of this visit? So that I can take a look at it?
I just want to mention 2 important things when it comes to network contribution:
- The bandwidth detection is not executed for each and every page action and therefore it can happen that the calculation might be a bit off track
- The blocks in the timeline that you see for the server side PurePaths is the end to end response time and this also contains the time the webserver needs to write the response on the network - hence we consider IO-time on the webserver as part of the network time.
Hope that helps.
Klaus
The Response Time of a User Action PurePath is time measured by our Browser Agent and it indicates the Response Time as experienced by the End User. So - a User Action called "Click on Submit" can be 1000ms. Linked with that User Action you can have 0 or many Server-Side PurePaths. The Server-Contribution is the sum of those PurePaths that had an impact on the Response Time perceived by the end user. What does that mean? There are server-side PurePaths that may not directly impact Response Time such as Asynchronous activities in the background or server-side requests that are completely executed asynchronously (or delay loaded).
More information can be founde in the doc:
As we keep getting more and more questions about the types of UEM Metrics we have, what they mean and how they get calculated our team is currently working on adding this information to the doc for the upcoming dynaTrace 6 release
Andi
So, then, in the User Action dashlet, is the Response Time (ms) metric the sum of server contribution + network time contribution?
Or it is still the sum of server+network+client?
Hi. There still is the Estimated Client Time Measure that you can put on a chart. The reasoning behind is that it is hard to really tell you how much time was spent on the client vs. network vs server. Server is clear because we have the server-side PurePaths with exact measurement. Network Time is also an estimate becuase we calculate it based on the bandwidth and size. Client Time is then the remaining time when you take the overall Response Time of the User Action minues Network Contribution and Server Time.
A more detailed description of these measures can be found here: User Action PurePaths
