UEM Timing measures split by Tagged Web Request or Synthetic Test Step
I am working with a load testing customer, the overall response time from load test result seems high on average. the actual user experience seems not as bad as the load test result. As you know the load test scripts calculate all the timing factors such as server, network and third party. Customer is more interested on the true user experience of the load test scenario.
The idea data breakdown is to chart total time, server time, client time, perceived render time by script step.
The only close thing I can find is to chart those time by page action URL (which are all loading type). I do not see a way to split the UEM timing data such as perceived render time, document interact time by Tagged Gomez script step or server purepath. Any help will be appreciated.
If the above request is not doable, is there a way to chart perceived render time (and or total time, network time etc) split by page action name?
Thanks
Dong
Hi. Have you looked at Gomez APM Integration?
There are some out of the box Business Transactions and Dashboards that you get in dynaTrace that will give you the information you request. It splits UEM User Actions by Test and Step Names
Andreas, Thanks, I reviewed the section but cannot find the charts/dashboard I need. I need to chart the timing (perceived render time specific) by Step Names (Gomez synthetic Test). Thanks
Hi Liu,
The problem is that a script step can consist of multiple user actions and you are right on a server side PurePath you do not have perceived render time,...
What you can do is create a visit based BT that splits by page action name or page action target URI. This would allow you to calculate the values for total time, server time,...
Cheers Klaus
Thanks Klaus.
I played around with a test, seems a page action based BT split by Tagged web requests works as I expected. See link at Re: Perceived Render Time by Synthetic Test Steps
Using visit based BT will return the same value for each tagged request (Tagged Web Request split by NA). Use page action BT seems return the average data
