Terminology in UEM (Nav Specs)
Hi,
Can someone help me with the below questions.
Question1: We have UEM and we have turned on Navigation timings. There are different terms like Client time, load time, etc. i could not find definitions for these. Are there any articles describing these.
Questions2: In page action purepaths one of the column is "Compare to Baseline", how can i find what is the actual baseline value it is being used? also can i chart the actual times vs baseline times?
Questions3:Also i am seeing a POST request with dynTraceMonitor for lot of requests. What is the use for this? one example is below.
POST /search/ecatalog/N-/dynaTraceMonitor?actions=1%7Cclick%2520on%2520%2522Add%2520to%2520Cart%2522%7C-%7Cclick%7C1357579943734%7C1357579946515%7C2778$fId=408667250_120$rId=RID_275078549$rpId=-938886902$dtV=3142$domR=1357579876421$3p=s.thebrighttag.com%7C0%7C0%7C0%7C%7C0%7C0%7C0%7C1%7C78391_78938%7C547%7C547%7C547%7C0%7C%7C0%7C0%7C0%2Cs%7C78391%7C78938%7Cundefined%7Chttps%253A%252F%252Fs.thebrighttag.com%252Ftag%253Fsite%253DzvYfmT0%2526docReferrer%253Dhttps%25253A%25252F%25252Fnew.grainger.com%25252Fsearch%25253FsearchQuery%25253Drust%25252Bremover%2526cf%253D5014%25252C8963%25252C8965%3Biocdn.coremetrics.com%7C0%7C0%7C0%7C%7C0%7C0%7C0%7C2%7C78391_78657_79469_81313%7C1055%7C266%7C1844%7C0%7C%7C0%7C0%7C0%2Cs%7C79469%7C81313%7C%7Chttps%253A%252F%252Fiocdn.coremetrics.com%252F90000010%252FV4%252FP31202%252FPEA%252FEA1E0B7F.js%253FV%253D2013010612$time=1357579952109$
Hi,
Q2 is the Performance Basline that you can configure in the UEM Config dialog (see screen below). It is the threshold for the APDEX calculation as well.
Klaus
Hi,
I can answer Q1 and Q3...
Q1 - see the following doc page: https://apmcommunity.compuware.com/community/display/DOCDT50/W3C+Navigation+Timing+Metrics
Q3 - This is how we transfer the metrics from the client side (the browser) to the dynaTrace infrastructure. Those POST requests are handled by the dynaTrace agent (web server or Java) and the extracted data points are then sent to the collector/server.
Best, Roman
Hi Roman,
Thanks for your answers. I have read the article that you have mentioned for Q1 but that does not have what are client time, load time, etc.
Apologies, the link indeed covers only the W3C navigation timinings. How about this one - https://apmcommunity.compuware.com/community/display/DOCDT50/Page+Actions? I covers the client time, network time metrics that the page action dashlet shows...
On Q2 - the baseline here actually refers to the value you have configured in the UEM configuration screen (either a static, custom value or a SpeedOfTheWeb benchmark). This column just visualizes how this specific PP did compared to the baseline - green is below the baseline, yellow between the baseline and 4x the baseline and red is above 4x the baseline.
Best, Roman
Thanks Roman. This is helpful. What is the difference between load time and client time? i was thinking load time is the total time required to load that page? but when i chart, client time is even higher than load time. Also do you know what is the difference between Network Latency and Network time? difference between processing time and server time?
I am a bit lost - can you post a screenshot where you got the metrics from? Are you still on the UEM dashlets only or also looking at the browser agent dashlets?
Gotcha - the easiest is to doubleclick the measure and take a look at the description. It often is quite good explanation of the measure.
Client time - the time spent on the client side (browser)
Load time - this is the total time for the whole page action
Network latency - the delay of network communication
Network time - how much time was actually spent transfering the page content
Server time - this is how long the request took server side, as measured by the agent
Thanks Roman.
Load time says,
Load time - this is the total time for the whole page action
and client time - the time spent on the client side (browser)
is it possible to have client time more than load time? that is what i am seeing..
No, load time should be higher than the client time. I would suggest you open a support case for that to have an engineer take a look at that. If possible include the PurePath where you are seeing this so they can try to figure out what is going on here.
Best, Roman
Will do that Roman. i was just going thru the definitions.
For Processing, it says -Represents the amount of time spent for resolving domain names (window.performance.loadEventEnd - window.performance.domLoading).
I thought DNS does that. is that right?
I also stumbled over that one, I think the resolving domain names is a wrong description here. Looking at the W3C processing model (which matches the event names given in the description) makes more sense - https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html#processing-model
Bascially the time between the response being delivered and the OnLoad event.
Best, Roman
Last question 
ideally i was thinking client time is equivalent to load time.
do you know how are they different?
for example is Load time sum of server+network+client time?
How is Client time calculated.
Hi,
Measure Load time/Metric Total Time is the sum of server + network + client time.
Important to know for the calculation of the client time is that we only calculate network time if bandwidth detection is turned on. Why is this important because client time = total time - server time - network time
So in case you have not turned on bandwidth detection the network time shown in the client is always "0" and instate of the separate number it is part of the client time
Thanks Klaus. It is clear now. We have turned on b/w calculation but every 30 mins. So does that mean only every 30 mins total time includes network time and rest of the time it is 0?
No! This means that for a visit that lasts longer than 30 min we do the bandwidth calculation again. eg: visit lasts 65 min -> dynaTrace will check the bandwidth 3 times.
the total time always includes the network time but if there is no bandwidth we cannot calculate the network time and it then and only in this case be part of the client time.
Hi,
I think things got mixed up here.
Roman is talking about the out of the box measure with the name "load time" and Venkata is talking about the metric "DOM Load Time"
MEASURE Load Time:
This measure is using the metric "Total Time" which represents the total time of a page action which is definitely bigger than the "client time".
METRIC DOM Load Time:
This metric gives you the time it takes till the Browser triggers the "Document Ready Event".
Both metrics do not refer to the W3C navigation timings.
Klaus
