cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

XHR noise filtering

mohamed_ayadi
Newcomer

Hi Andreas,

what is the 168571 ms means? and does that reflect the actual the user experience and page response time, and user waiting time for the page to render?

3 REPLIES 3

andreas_grabner
Dynatrace Guru
Dynatrace Guru

This means that this XHR Request took 160s to execute which means that this probably then resulted in some of the Browser Errors you see. XHR Requests are often triggered asynchronously to load something in the background. Probably also happens on this use case as the XHR is called in onload.

It is hard to say whether it impacts overall end user experience or not. You should ask the developers what that request is supposed to do. based on the URL it seems like something around querying for current notifications. So - maybe nothing critical for the initial page load time

Andi

mohamed_ayadi
Newcomer

thank you Andreas for the quick response. I checked with them, and they are those are async calls...how can we filter out AJAX async requests to get the true user percieved experience?

Sorry for the late reply. It is a bit hard to judge what the perceived render time could or should be based on the small screenshot you added. Any chance you can export your visit or user action? Feel free to send it to me as explained here: http://bit.ly/sharepurepath