1.
Click to download and the packet capture page cannot be opened.
Answer: Keep it for up to seven days
2.
There is no data after Stress testing ends, possible reasons
Answer: Pay attention to the validity period of the task. The validity period must be longer than Stress testing time. For example, if Stress testing is at 12 noon on January 1, then the task validity period must be after 12 o'clock. Otherwise, operation and maintenance will be able to execute Stress testing normally, but the scheduler will not issue this task.
3.
Page tasks There may be a part of blank time before the blocking time. Why is this?
Answer: The browser also needs some time when initializing the page and other actions. This part of the time has nothing to do with the customer's various indicators. This may have something to do with the performance of Probe (the answer is more or less this time, absolutely). If the customer is very concerned, just ignore Client Time. Total Download Time will become smaller, but First Contentful Paint (FCP) will not change at this time.
4.
The designated DNS of Instant Testing does not take effect.
Answer: Available on XP and WIN7 or above (WIN7 cannot)
5.
Is there a limit on the number of API calls?
Answer: Yes, the default is 500 times per day
6.
Streaming media security channel support error
Answer: It is possible that the system time of Probe is inaccurate, causing the problem. Instant Testing open debug
7.
Deleting the sub-account and re-creating it will prompt that the user name already exists.
Answer: The reason is that our server will not modify the database in real time. I will accumulate these to a certain extent and modify them together later. As for how long it will take, we are not sure. If you want to use it immediately, you can only find the backend and change the account name that previously existed in the database to any character, so that there will be no conflict. You can recreate it immediately.
8.
An unknown Error such as 600XXX appears.
Answer: This type of Error is generally an HTTP status code run out by the server that does not exist in our Error code base. The code of page Error404 is 600404 and we definitely don’t know if it is customized by the customer. So directly display 600XXX, you can turn on the report capture and look at the response status code of Request from the packet capture.
9.
The self-owned Probe client has Error problems such as IE being occupied and unable to run.
Answer: First close the client, then open the Synthetic Tasks server, kill all IE processes, and then restart the client.
10.
Probe error message cannot establish connection with the server (Host IP is an IPv6 address).
Answer: You can avoid IPv4 Probe from accessing IPv6 Host by selecting "Only use IPv4 Probe" in the task. The default is to select "IPv4/IPv6 mixed mode"
11.
Application certificate is invalid
Answer: It is recommended to try chrome. Older versions of XP systems do not support HTTPS very well, and you may get this Error error when using IE.
12.
How many IPs can be included in the IP whitelist?
Answer: About 2000 bytes, estimated to be about 600 IPs (if you have to write this or that many, you can calculate the exact value yourself)
13.
Can our Probe be pinged?
Answer: Not necessarily. But this is meaningless. IDC may ban ping. LM's IP is dynamic. If it is a customer inquiry, just reply directly: We do not provide this service, and it is normal for the ping to fail.
14.
Can different sub-accounts only see the tasks assigned by themselves?
Answer: Unfortunately, you can't see all the tasks assigned to the package. If you want to ensure that each sub-account can only see and manage its own tasks, it would be very troublesome to open an independent package for each sub-account so that they do not interfere with each other.
15.
The number of Probe displayed on the report is less than the number of visits obtained by customer Host
Answer: Customer Host only recorded a few visits, but our report may encounter many situations before the data is stored in the database, such as trace volume, noise, and resending. Therefore, our report also has an indicator called the storage rate. For example, 90 of 100 should be sent to the database, which means 90% is stored in the database. However, the customer may have 100 records or even 101 records (we will reissue a visit in one case)
16.
When streaming media playback, it is found that the HTTPS task does not have SSL Handshake Time.
Answer: We bought a third-party service to help parse the streaming media page. The response is HTTP, so there will be no handshake time.
17.
The connection to the server is reset
Answer: From some packet captures, we found that if the customer has requirements for the SSL version during the SSL Handshake Time, such as TLSV1.0 and above, then the Request sent by Probe that only supports SSL2.0 or SSL3.0 will be RST dropped by the server. Of course this is only one possibility
18.
What determines whether Probe accesses Host with IPv6 or IPv4?
Answer: Which Host to connect to is determined by the browser itself, because we control what kind of DNS (A or AAAA) Request is sent by Probe, but we do not control who Probe establishes a connection with.
19.
How to achieve using only IPv6?
Answer: If we do not specify Probe mode (mixed mode):
20.
Chrome usually sends A first, and then AAAA if it supports IPv6.
21.
IE usually sends A and AAAA together, wait for the result before connecting again.
If you specify IPv6 Probes:
22.
Probe will only send AAAA Request.
23.
How does Tingyun ensure that the cache is cleared every time Request is accessed?
Answer: Under the IE kernel, a system function will be called before each Request access to directly clear the computer's own cache. However, due to different policies, Chrome must initiate DNSRequest every time it is accessed instead of going through the cache.