Response Time Difference, likely a configuration problem?
We are exploring using UEM in one of our important applictions, part of this is to investigate the accuracy of the infromation being gathered. Our business partners have applied a method of reporting response times from the client to a custom database to measure how this application is behaving. We have run into a a pretty sizable difference.
One of the calls being made from the page load user action is reporting a response time of 29ms, which is accurate when measured from the webserver, however, the data being asked for is the overall impact to the customer. In this event, this call is being made as part of a larger java operation, which is taking approximately 500ms. Is there a correct setting I am missing where the java operation can be reported in addition to just the request to the back end?
This is on version 5.6.
Hi Brian
Any chance you can export this User Action into a dynatrace session and attach it?
This request seems to have a significant asynchronous part.
Are you saying that you are missing the 'Java Operation' on the client side that is issuing the call(s)?
Thanks. Now - can you let me know which call should take 500ms? Is that something this request /rsAccountService/rest/... triggers asynchronously? Or where would you expect that 500ms?
It is triggered asynchronously, however it is being reported that the call is actually part of a larger java operation on the browser. That additional logic is consuming near the entire half second with this call only the 29ms. So in essence what my LOB business folks are looking for is the time the client side javascript in addition to this service call as a response time. I am trying to gain more details.
Hi Brian
Thanks for the explanation. If I look at the details of the User Action -> via the Context Menu on the User Action PurePath Node that is called "Loading of page ... I can see that 1.55s of the 2s are spent in processing. That means the browser was actually proceessing data including JavaScript.
So - if you want to do more diagnostics on JavaScript execution I suggest you use our Browser Agent. I wrote a blog about it and also recorded a video on how to use the Browser Agent to diagnose performance problems that happen in the browser:
- Video: https://www.youtube.com/watch?v=dC8LXRHZvq8&list=PLqt2rd0eew1bmDn54E2_M2uvbhm_WxY_6&index=9
- Blog: http://apmblog.compuware.com/2014/12/11/dynatrace-ajax-edition-4-5-last-page-chapter-yet-story-continues/
Andi
