Applicable product: Tingyun Network (Synthetic Monitoring)
Applicable scenarios: The monitored website uses a CDN/WAF service such as Cloudflare, and has features such as human verification or bot protection enabled, causing synthetic tasks to fail or producing abnormal data.
Task scheduling center → Probe receives the task → Probe browser / probing engine accesses the target → Performance data is collected → Data is sent back to the data center → Presented in reports| Probe type | Description |
|---|---|
| IDC Probes | Deployed in data centers. The network environment is stable and controllable, and is suitable for baseline testing |
| Last Mile Probes | Endpoints on real user networks, closer to the end-user access experience |
Note: This is a normal conflict between security protection policies and automated monitoring. It does not mean the website itself is down, nor does it mean the synthetic data is inaccurate. The solution is to have your security policy identify and allow Tingyun synthetic traffic while keeping protection in place for other traffic.
X-Tingyun-Monitora8F3kQ9zLm2Xp7Vt (generate your own; do not use the sample value)X-Tingyun-Monitor equals the value you set in Step 1. In the expression editor, you can enter:any(http.request.headers["x-tingyun-monitor"][*] eq "YOUR_CONFIGURED_VALUE")YOUR_CONFIGURED_VALUE with the value you set in Step 1.)TingyunMonitor to the end of a standard browser UA), and then create a skip rule in Cloudflare based on that UA.Note: A UA is easy for others to imitate, so this is less secure than Option 1. Use it only as a temporary measure, or combine it with other conditions.