Report Data Does Not Match Customer Server Statistics

Detailed description of the problem

In the Error Overview page, it is found that there are many task timeouts (Element) Error, but at the same time, the data returned by the client and server has a status code of 200. The client questions the data.

Troubleshooting process

Check the Probe time and the Log on the server side, and compare it to find that the server is responding normally. Checking the HTTP header information of Probe, the response header is received normally, but when Request reaches the second Element, "task timeout (Element)" Error occurs.

Why is the icon Request?
If the phone's operating system version is high (Android 4.4 or above), the icon in the Request page settings will be displayed.
Note: The pictures in the Request page settings are the default rules of high-version Android systems and have nothing to do with browsers and clients.

Why does the server http200, but Request detect Element, report an error "task timeout (Element)"?
Answer: We determine the timeout based on two conditions. One is that this monitoring triggers onpagefinish event, and the monitoring ends. However, the Request of the Request picture is not completed, and an error "task timeout (Element)" will be reported;
The other is the timeout caused by Request not getting the required data.

Solution

(1) In the report, Request and a certain Element report "task timeout (page)". Please ignore the Element error caused by this Element.
(2) Filter this Element in task settings and do not monitor this Element.

Report Data Does Not Match Customer Server Statistics

Detailed description of the problem#

Troubleshooting process#

Solution#

Detailed description of the problem

Troubleshooting process

Solution