Cloud Monitor:Monitor sites from mobile detection points

Background

• If your site uses a firewall allowlist, add detection point IP addresses to prevent blocking. How to add probe requests to an allowlist when they are mistaken for attacks or crawlers.

• Mobile detection points provide:

  • Real mobile networks

    Probe target sites over real cellular networks of China's three major carriers to measure availability and latency.

  • Extensive mobile detection point resources

    Over 300 detection points across 100+ cities in China, covering China Telecom, China Mobile, and China Unicom.

  • Non-intrusive deployment

    No script embedding required. Works out of the box.

Steps

1. Log in to the Cloud Monitor console.

2. In the left navigation pane, go to network analysis and monitoring > Site Monitoring.

3. On the monitoring task tab, select new task, and then click single-step probe.

4. On the Create Task page, select Mobile and configure the settings for your mobile site monitoring task.

   • Basic information

     • Task type: HTTP(S)

       Parameter	Description
       DtsJobName	The task name. Must be 4–100 characters and can include letters, digits, underscores (_), and Chinese characters.
       Monitored address	The target URL to monitor. Supported request methods: GET (default) POST HEAD To monitor multiple URLs, enter one per line.
       Frequency	The monitoring frequency. Valid values: 1 minute and 5 minutes. If you select 1 minute, each detection point probes the target once per minute.
       Advanced settings	See the following table. Important Due to handshake protocol vulnerabilities, Cloud Monitor no longer supports TLS versions earlier than 1.2, aligning with mainstream browser standards. If a site monitoring task reports the error tls: server selected unsupported protocol version 302 and you do not want to upgrade your server's TLS protocol, you can select a compatible minimum TLS version on the Others subtab in the advanced settings.

       Advanced settings for HTTP(S) tasks:

       Subtab	Parameter	Description
       Request parameters	HTTP request header	The HTTP request header in the key1:value1 format. Separate multiple headers with line breaks. Site monitoring adds the following default headers to the request: Host:${domain name in monitored address} Pragma:no-cache Cache-Control:no-cache User-Agent:Chrome/57 Accept: */* If the request content is a form, the following header is also added: Content-Type: application/x-www-form-urlencoded;charset=UTF-8 If your custom headers include any of these default headers, your settings override the default ones. Note In compliance with the HTTP protocol, site monitoring converts the keys in the request headers that you provide to the canonical MIME header format: The first letter and any letter that follows a hyphen (-) are capitalized. For example, accept-encoding is converted to Accept-Encoding. If a key contains spaces or other invalid characters, the key remains unchanged.
       	Cookie	The cookie content for the HTTP request.
       	Request content	The content of the request body. The content can be in the key1=value1;key2=value2 format or in JSON format, such as {"test":"testValue"}. Note When the Request method is set to POST, this parameter is required.
       	Unfollow redirect	Whether to follow HTTP 301 and 302 redirects. Redirects are followed by default.
       	Certificate verification	Whether to enable Server Name Indication (SNI). Disabled by default.
       User authentication	HTTP authentication username	The credentials for basic HTTP authentication.
       	HTTP authentication password
       Others	Enable PROXY protocol	Whether to enable the PROXY protocol. Disabled by default.
       	Minimum TLS Version	Minimum TLS version supported. Valid values: tlsv1.0 tlsv1.1 tlsv1.2 tlsv1.3
       	Matching response mode	Site monitoring searches for the specified text within the first 64 KB of the HTTP response body. Available modes: Alert if response contains matching content Alert if response does not contain matching content The content to match must consist of only English characters.
       	Match response content
       	Acceptable HTTP status codes >= 400	HTTP status codes (400 or higher) treated as successful responses. No alert is triggered for these codes. Separate multiple codes with commas (,).

     • Task type: PING

       Parameter	Description
       DtsJobName	The task name. Must be 4–100 characters and can include letters, digits, underscores (_), and Chinese characters.
       Monitored address	The target address to monitor. Can be a domain name or IP address. To specify multiple addresses, enter one per line.
       Frequency	The monitoring frequency. Valid values: 1 minute and 5 minutes. If you select 1 minute, each detection point probes the target once per minute.
       Number of ping packets	The number of ping packets to send in each probe. Default value: 10.

     • Task type: DNS

       Parameter	Description
       DtsJobName	The task name. Must be 4–100 characters and can include letters, digits, underscores (_), and Chinese characters.
       Monitored address	The target domain name to monitor. To specify multiple domain names, enter one per line.
       Frequency	The monitoring frequency. Valid values: 1 minute and 5 minutes. If you select 1 minute, each detection point probes the target once per minute.
       Type	The type of DNS query. Valid values: A (default) MX NS CNAME TXT ANY AAAA
       DNS access protocol	The transport layer protocol used for DNS queries. Valid values: udp (default) tcp tcp-tls
       Expected resolution result	The probe succeeds if the actual DNS resolution results contain all specified domain names or IP addresses. Separate multiple domain names or IP addresses with commas (,).
       Matching rule	The matching rule for the domain name or IP address.
       Port	The port number of the DNS server to query.

   • Assertion

     When the task type is HTTP(S), assertions define availability conditions based on probe response content. A probe succeeds only when all conditions are met.

     Note

     • For HTTP probes, if you do not set an assertion for the status code, a status code below 400 indicates availability by default.

     • You can use assertions with the following protocols: HTTP(S), PING, WebSocket, DNS, TCP, and UDP.

     CloudMonitor provides one default availability condition. To add more:

     1. Click Add Condition Group.

     2. Configure the availability conditions for the assertion.

        • Response time: Checks if the response time is acceptable. Default: Less than 5,000 ms.

        • Status code: Checks if the response status code is acceptable. Default: Less than 400.

        • Header: Checks if a specified field in the response header matches an expected value.

        • Body, Body XML field, or Body JSON field: Checks the response body content by using text matching, XML parsing (XPath), or JSON parsing (JSONPath).

     3. Click Availability Test. The test results appear on the right.

        • If the availability test is successful, you can create the site monitoring task.

        • If the availability test fails, you can run network diagnostics from the corresponding probe point.

     If a response does not meet the conditions, run PING and MTR (My traceroute) diagnostics from the corresponding probe point.

     Note

     MTR combines PING and Traceroute functionality.

     Distributed tracing: Supported only for HTTP(S) tasks. Managed Service for OpenTelemetry Integration Guide.

     • Tracing upload endpoint: Select the destination region for your trace data.

     • Tracing protocol: Supported protocols include OpenTelemetry W3C, Zipkin B3, and Jaeger.

   • Select probe points

     Parameter	Description
     IP Probe Type	The IP probe type for the probe point. Valid values: IPv4, IPv6, IDC, and LastMile.
     Select Probes	The default and custom probe points for site monitoring. If the default CloudMonitor probe points do not meet your needs, create a custom template: Click Manage Custom Templates. Click Create Template. Enter a Template Name and select the desired probe points. Click OK. Click OK.

   • Configure an alarm rule

     CloudMonitor provides a default alarm rule. To create a custom rule:

     1. Click Add Rule.

     2. Configure the parameters for the rule.

        Parameter	Description
        Rule name	The name of the alarm rule.
        Metric name	The metric that triggers the alarm. Valid values: availability percentage Calculated as: (Successful probes / Total probes) × 100% per monitoring cycle. Number of unavailable probes The number of failed probes for the monitored resource in a monitoring cycle. Number of available probes The number of successful probes for the monitored resource in a monitoring cycle. Any error code (independent alert) Triggers an alert if the result from any probe point matches the specified status code. All error codes (combined alert) Triggers an alert only if the results from all probe points match the specified status code. response time
        Comparison operator	The operator used to compare the metric's value to the threshold. Valid values: >= > <= < = != Increase from the same time yesterday Decrease from the same time yesterday Increase from the same time last week Decrease from the same time last week Increase from the previous period Decrease from the previous period
        Threshold and alert level	The alert level and its corresponding threshold. For the alert level Info, the notification methods are Email + Webhook. The number of consecutive times the condition must be met to trigger an alert.
        Tags	Tags for categorizing the alarm rule.
        Auto Scaling	If you enable Auto Scaling, an alert triggers the corresponding scaling rule. You must specify the Region, ESS Group, and ESS Rule. To learn how to create a scaling group, see Configure a scaling group. To learn how to create a scaling rule, see Configure a scaling rule.
        Log Service	If you enable Simple Log Service, alert notifications are sent to the specified Logstore when an alert occurs. You must specify the Region, Project, and Logstore. To learn how to create a Project and a Logstore, see Use Logtail to collect and analyze text logs of ECS instances.
        Message Service (MNS) - topic	If you enable Simple Message Queue (formerly MNS) - Topic, alert notifications are sent to the specified topic when an alert occurs. You must specify the region and topic. To learn how to create a topic, see Create a topic.
        Function Compute	If you enable Function Compute, alert notifications are sent to the specified function for processing when an alert occurs. You must specify the region, service, and function. To learn how to create a service and a function, see Quickly create a function.

     3. Click OK.

   • Alert contact groups

     Parameter	Description
     Alert Contact Group	The alert contact group that receives notifications. Select at least one. An alert contact group contains one or more alert contacts.
     Silence Period	The time to wait before resending a notification for an unresolved issue. Valid values: 5 minutes, 15 minutes, 30 minutes, 60 minutes, 3 hours, 6 hours, 12 hours, and 24 hours. When a metric reaches the alert threshold, CloudMonitor triggers an alert. No repeat notifications are sent during the silence period. After it ends, CloudMonitor resends a notification if the threshold is still exceeded. Note Click advanced settings to configure this parameter.
     Effective Time	The period when the alert rule is active and can trigger alerts. Note Click advanced settings to configure this parameter.
     Alert Webhook	A public URL that receives CloudMonitor alert notifications through HTTP POST requests. Only the HTTP protocol is supported. Use a threshold alert webhook. To test the webhook URL: Click Test next to the webhook URL. In the Webhook Test panel, use the returned status code and test results to verify and troubleshoot the URL. Note You can also set the Test Template Type: and Language:. Then, click Test again to view the results. Click Close. Note Click advanced settings to configure this parameter.

5. Click Create.

Related operations

Related documents

• Probing from public detection points

• Site monitoring detection point IP pool

• Error codes and status codes

• Metrics