Create a PC-based site monitoring task - Cloud Monitor - Cloud Monitor

Prerequisites

You have created an alert contact or alert contact group. Create an alert contact or an alert contact group.
To use alert callbacks, prepare a publicly accessible callback URL and enable it as a notification method in your O&M or notification system.

Background

Activate site monitoring and configure billing. Activate Network Analysis and Monitoring.
If your site uses a strict firewall or allowlist, add detection point IP addresses to prevent blocking. Add the IP addresses of detection points to a whitelist if detection requests are identified as attacks or web scraping.

Procedure

Log on to the Cloud Monitor console.
In the left-side navigation pane, choose Network Analysis and Monitoring > Site Monitoring.
On the Monitoring Tasks tab, click Create Task, and then click Single-step Detection.

On the Create Task page, select PC and configure the parameters for the site monitoring task.

Basic information

Task type: HTTP(S)

Parameter	Description
DtsJobName	The task name. Must be 4 to 100 characters: letters, digits, underscores (_), and Chinese characters.
Monitored address	The URL to monitor. Valid values: GET (default) POST HEAD The monitored address must be a URL. To monitor multiple URLs, separate them with line breaks.
Frequency	The monitoring frequency. Valid values: 15 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, and 60 minutes. Each detection point monitors the target at the selected interval. Custom intervals are also supported. Note If you activated pay-as-you-go Cloud Monitor (cms_post) or purchased a subscription Cloud Monitor package (cms_edition) before 22:00:00 (UTC+8) on September 13, 2022, you cannot set the frequency to 15 seconds. You must activate Network Analysis and Monitoring to use the 15-second frequency.
Advanced settings	Configure HTTP(S) parameters in Advanced settings. Important Handshake protocols earlier than TLS 1.2 have security vulnerabilities. Therefore, to stay consistent with mainstream browsers, Cloud Monitor no longer supports server-side TLS versions earlier than 1.2. If a site monitoring task fails with the error `tls: server selected unsupported protocol version 302` and you prefer not to upgrade the server's TLS protocol, you can select a compatible minimum TLS version on the Others tab under Advanced settings.

Task type: PING

Parameter	Description
DtsJobName	The name of the site monitoring task. It must be 4 to 100 characters long and can contain letters, digits, underscores (_), and Chinese characters.
Monitored address	The domain name or IP address to monitor. Separate multiple addresses with line breaks.
Frequency	The monitoring frequency. Valid values: 15 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, and 60 minutes. Each detection point monitors the target at the selected interval. Custom intervals are also supported. Note If you activated pay-as-you-go Cloud Monitor (cms_post) or purchased a subscription Cloud Monitor package (cms_edition) before 22:00:00 (UTC+8) on September 13, 2022, you cannot set the frequency to 15 seconds. You must activate Network Analysis and Monitoring to use the 15-second frequency.
Number of ping packets	The number of ping packets sent. Default: 10.

Task type: DNS

Parameter	Description
DtsJobName	The name of the site monitoring task. It must be 4 to 100 characters long and can contain letters, digits, underscores (_), and Chinese characters.
Monitored address	The domain name to monitor. Separate multiple addresses with line breaks.
Frequency	The monitoring frequency. Valid values: 15 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, and 60 minutes. Each detection point monitors the target at the selected interval. Custom intervals are also supported. Note If you activated pay-as-you-go Cloud Monitor (cms_post) or purchased a subscription Cloud Monitor package (cms_edition) before 22:00:00 (UTC+8) on September 13, 2022, you cannot set the frequency to 15 seconds. You must activate Network Analysis and Monitoring to use the 15-second frequency.
Type	The DNS query type. Valid values: A (default) MX NS CNAME TXT ANY AAAA
DNS access protocol	The DNS access protocol. Valid values: udp (default) tcp tcp-tls
DNS server	The DNS server type. Valid values: System default DNS Carrier DNS of the detection point Custom DNS
Number of retries after DNS failure	Retries after a DNS detection failure.
Expected resolution result	Cloud Monitor verifies that the DNS resolution contains your expected domain names or IP addresses. Detection succeeds when all specified addresses appear in the resolved list. Separate multiple domain names or IP addresses with commas (,).
Matching rule	The matching rule for the domain name or IP address. Valid values: All expected results must be included in the DNS response: The detection succeeds if the DNS response includes all expected results. Extra IP addresses in the response are allowed. This value is suitable for scenarios where a domain name resolves to multiple, dynamically changing IP addresses, such as when the domain name points to a CDN or a load-balanced service. All DNS responses must be included in the expected alias or IP addresses: The detection succeeds only if every address in the DNS response is included in your expected results, which limits the range of returned IP addresses. DNS responses must be identical to the expected alias or IP addresses: The detection succeeds only if the DNS response is exactly the same as your expected results. DNS responses must intersect with the expected alias or IP addresses: The detection succeeds if the DNS response and your expected results share at least one matching value. If the domain name resolves to a CDN, which typically returns multiple IP addresses that change dynamically, we recommend that you select All expected results must be included in the DNS response.
Port	The port of the DNS server.

Task Type: TCP or UDP

Parameter	Description
DtsJobName	The name of the site monitoring task. It must be 4 to 100 characters long and can contain letters, digits, underscores (_), and Chinese characters.
Monitored address	The IP address to monitor. Separate multiple addresses with line breaks.
Frequency	The monitoring frequency. Valid values: 15 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, and 60 minutes. Each detection point monitors the target at the selected interval. Custom intervals are also supported. Note If you activated pay-as-you-go Cloud Monitor (cms_post) or purchased a subscription Cloud Monitor package (cms_edition) before 22:00:00 (UTC+8) on September 13, 2022, you cannot set the frequency to 15 seconds. You must activate Network Analysis and Monitoring to use the 15-second frequency.
Port	The TCP or UDP port. The default value is 80.
Advanced settings	Configure TCP or UDP parameters in Advanced settings.

Task Type: SMTP or POP3

Parameter	Description
DtsJobName	The name of the site monitoring task. It must be 4 to 100 characters long and can contain letters, digits, underscores (_), and Chinese characters.
Monitored address	The domain name or IP address to monitor. Separate multiple addresses with line breaks.
Frequency	The monitoring frequency. Valid values: 15 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, and 60 minutes. Each detection point monitors the target at the selected interval. Custom intervals are also supported. Note If you activated pay-as-you-go Cloud Monitor (cms_post) or purchased a subscription Cloud Monitor package (cms_edition) before 22:00:00 (UTC+8) on September 13, 2022, you cannot set the frequency to 15 seconds. You must activate Network Analysis and Monitoring to use the 15-second frequency.
Port	The SMTP or POP3 port. The default value for SMTP is 25. The default value for POP3 is 110.
Username	The username and password of the SMTP or POP3 server.
Password	The username and password of the SMTP or POP3 server.
Secure connection	Whether to use a secure connection for SMTP or POP3. Valid values: Use Do not use

Task type: FTP

Parameter	Description
DtsJobName	The name of the site monitoring task. It must be 4 to 100 characters long and can contain letters, digits, underscores (_), and Chinese characters.
Monitored address	The domain name or IP address to monitor. Separate multiple addresses with line breaks.
Frequency	The monitoring frequency. Valid values: 15 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, and 60 minutes. Each detection point monitors the target at the selected interval. Custom intervals are also supported. Note If you activated pay-as-you-go Cloud Monitor (cms_post) or purchased a subscription Cloud Monitor package (cms_edition) before 22:00:00 (UTC+8) on September 13, 2022, you cannot set the frequency to 15 seconds. You must activate Network Analysis and Monitoring to use the 15-second frequency.
Port	The FTP port. The default value is 21.
Anonymous logon	Anonymous logon (default) Identity verification required If you select this option, you must specify the username and password of the FTP server.
Username	The username and password of the FTP server.
Password	The username and password of the FTP server.

Assertion definition
For HTTP(S) task type, define assertions to verify server responses. Set multiple availability conditions per assertion. Detection is available only when all conditions are met.
Note
- For HTTP detections, if you do not define an assertion for the status code, a status code less than 400 indicates that the site is available.
- Assertion definitions are supported for HTTP(S), PING, WebSocket, DNS, TCP, and UDP.
Cloud Monitor provides a default availability condition. To add a custom condition:
1. Click Add Condition Group.
2. Configure the availability conditions for the assertion.
  - Response time: determines whether the response time meets expectations. Default: less than 5,000 ms.
  - Status code: determines whether the response status code meets expectations. Default: less than 400.
  - Header: determines whether the fields in the response header meet expectations. You must customize the response header.
  - body, body's XML field, and body's JSON field: check whether response body content meets expectations through text matching, XML parsing (XPath syntax), and JSON parsing (JSON Path syntax).
3. Click Verify. You can view the verification result in the right-side pane.
  - If the verification is successful, you can proceed to create the site monitoring task.
  - If the verification fails, you can initiate a network diagnostic probe from the corresponding detection point.
If a response does not meet the specified conditions, you can initiate PING and MTR network diagnostic probes from the corresponding detection point.

Note
MTR is a network diagnostic tool that combines the features of PING and traceroute.
Enable Tracing Analysis: Enable tracing for HTTP(S) tasks. Integrate with OpenTelemetry.
- Ingest endpoint: Select a region based on your requirements.
- Tracing protocol: The supported protocols include OpenTelemetry W3C, Zipkin B3, and Jaeger.

Select detection points

Parameter	Description
IP probe type	The IP probe type of the detection points. Valid values: IPv4, IPv6, IDC, and LastMile. Detection points with the IPv6 probe type are also compatible with IPv4 target addresses. No additional configuration is required.
Select detection points	The default and custom detection points for site monitoring. To customize detection points: Click Manage Custom Templates. Click Create Template. Enter a Template Name and select custom detection points. Click OK. Click OK.

Set alert rules

Cloud Monitor provides a default alert rule. To create a custom rule:

Click Add Rule.

Configure the parameters for the rule.

Parameter	Description
Rule name	The alert rule name.
Metric name	The metric for the alert rule. Valid values: Percentage of available detection points Percentage of available detection points = (Number of successful detections / Total number of detections) × 100%. Number of unavailable detection points The number of detection points that failed to access the target domain or IP address during a detection cycle. Number of available detection points The number of detection points that successfully accessed the target domain or IP address during a detection cycle. Any error code (independent alert) An alert is triggered if the detection result from any detection point matches the specified status code. All error codes (combined alert) An alert is triggered only if the detection results from all detection points match the specified status code. Response time
Comparison	The threshold comparison operator. Valid values: >= > <= < = != Day-over-day increase Day-over-day decrease Week-over-week increase Week-over-week decrease Period-over-period increase Period-over-period decrease
Threshold and alert level	The alert level and the corresponding threshold. For the Info level, notifications are sent by email and WebHook. The number of consecutive times the condition must be met to trigger an alert can be 1, 2, 3, 4, 5, 10, 15, or 20.
Tag	The tag of the alert rule.
Auto Scaling	If you enable Auto Scaling, Cloud Monitor triggers the associated scaling rule when an alert occurs. You must specify the Region, ESS Group, and ESS Rule. Configure a scaling group. Configure a scaling rule.
Simple Log Service	If you enable Simple Log Service, Cloud Monitor sends alert data to a Logstore in Simple Log Service (SLS) when an alert occurs. You must specify the Region, ProjectName, and Logstore. Collect and analyze ECS text logs using LoongCollector.
Message Service (MNS) topic	If you enable Simple Message Queue (formerly MNS) - Topic, Cloud Monitor sends alert data to a Message Service (MNS) topic when an alert occurs. You must specify the region and topic. Create a topic.
Function Compute	If you enable Function Compute, Cloud Monitor sends alert notifications to Function Compute (FC) for custom formatting when an alert occurs. You must specify the region, service, and function. Quickly create a function.

Click OK.

Configure alert contact groups

Parameter	Description
Configure alert contact groups	Alert contact groups that receive notifications. Select at least one group. Notifications are sent to all contacts in the selected group.
Mute period	The interval to wait before resending a notification for an unresolved alert. Valid values: 5 minutes, 15 minutes, 30 minutes, 60 minutes, 3 hours, 6 hours, 12 hours, and 24 hours. When a metric exceeds its threshold, a notification is sent. No further notifications are sent during the mute period. If the alert persists after the mute period, another notification is sent. Note Click Advanced settings to configure this parameter.
Effective period	The time period during which the alert rule is active. Note Click Advanced settings to configure this parameter.
Alert callback	A publicly accessible URL that receives alert data from Cloud Monitor via HTTP POST requests. Only HTTP is supported. Use threshold-based alert callbacks. To test connectivity to the callback URL: Click Test, located directly to the right of the callback URL. In the WebHook Test panel, check the HTTP status code and test result details to verify connectivity. Note You can also set the Test Template Type: and Language:. Then click Test again to view updated test results. Click Close. Note Click Advanced settings to configure this parameter.

Click Create.

Related operations

If a detection returns assertion failed, view the cause:

On the Site Monitoring page, on the Monitoring Tasks tab, click the name of the target site monitoring task.
On the Overview page, click the Error tab in the detection results section.
In the Actions column for the target detection point, click Details to view the cause of the assertion failure.

Troubleshooting

How to determine whether an alert is caused by a node failure or a target site issue

If multiple monitoring tasks report alerts at the same time, follow these steps to determine where the failure originates:

On the detection results of the monitoring task details page, filter detection records by carrier.
Compare the detection results of the detection points from different carriers. If only the detection points of a specific carrier fail while the detection points of other carriers are normal, the issue is usually a link issue between that carrier and the target IP address, not a failure of the target site.
Use the one-time probing tool to launch an instant detection against the target address to check whether the issue can be reproduced.

TCP connection timeout on a single node

If a detection point in the detection results reports a TCP connection timeout (error code 610), follow these steps to troubleshoot:

On the Error tab of the detection results, view the error message for the detection point.
Compare the detection results of detection points from other carriers to the same target. If the other detection points are normal, the target site is available.
Use the one-time probing tool to launch instant detections from different detection points against the target to check whether the issue can be reproduced.

Transient link failures

If the issue cannot be reproduced by an instant detection, it may be a transient link failure. Keep monitoring the subsequent detection results of the detection points from the same carrier and check whether the issue recurs.

References

Advanced settings

Advanced settings for each monitoring type:

HTTP(S)

Tab	Parameter	Description
Request parameters	HTTP request header	The format of an HTTP request header is `key1:value1`. Use line breaks to separate multiple headers. Site monitoring pre-populates the request with the following headers: `Host:${Domain name in the 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 included: `Content-Type: application/x-www-form-urlencoded;charset=UTF-8` Custom headers override the defaults. Note In compliance with the HTTP protocol, Site monitoring converts the keys in the request header to the canonical format of a MIME header: The first letter and the 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 text for the HTTP rule.
	Request content	The request content, which can be in the format of `key1=value1;key2=value2` or a JSON snippet such as `{"test":"testValue"}`. Note When Request Method is set to POST, you must set this parameter.
	Do not follow redirects	Whether to follow redirects when a 301 or 302 status code is returned. Not selected by default (redirects are followed).
	Certificate verification	Whether to support Server Name Indication (SNI). Not selected by default, which indicates that SNI is not supported.
User authentication	HTTP authentication username	The credentials for basic authentication over HTTP.
User authentication	HTTP authentication password	The credentials for basic authentication over HTTP.
DNS Server	DNS server	The IP address of the DNS server.
Others	Enable ProxyProtocol	Whether to enable the proxy protocol. Not selected by default, which indicates that the proxy protocol is not supported.
	Minimum TLS Version	The minimum TLS version compatible with Cloud Monitor. Valid values: `tlsv1.0` `tlsv1.1` `tlsv1.2` `tlsv1.3`
	Response match method	If you provide content to match, Site monitoring searches for it within the first 64 KB of the response body. Valid values: Alert if response contains matched content Alert if response does not contain matched content Site monitoring determines whether to trigger an alert based on the selected response match method. The matched content must be in English.
	Response content match
	Acceptable HTTP status code greater than or equal to 400	An HTTP status code that is 400 or greater. To specify multiple status codes, separate them with commas (,).

TCP or UDP

Parameter	Description
Request content format	This parameter applies only when the request content is not empty. Valid values: Text Hexadecimal format
Request content	Text A string that consists of visible characters. Note Plain text does not support escape characters. For example, `\n` is treated as two separate characters, `\` and `n`, not as a line break. Hexadecimal format If the request content is a byte string that cannot be expressed in visible characters, you can convert the byte string to a visible string in hexadecimal format. For example, `(byte)1` is converted to `01`, and `(byte)27` is converted to `1B`. A binary array in Java format, such as `{(byte)1, (byte)27}`, is converted to `011b` or `011B`. Site monitoring is not case-sensitive to hexadecimal characters. Enter the string `"011B"` in the Request content field and select Hexadecimal format for the Request content format parameter.
Response content match format	This parameter applies only when the response content is not empty. Valid values: Text Hexadecimal format
Response content match	Text A string that consists of visible characters. Note Plain text does not support escape characters. For example, `\n` is treated as two separate characters, `\` and `n`, not as a line break. Hexadecimal format If the request content is a byte string that cannot be expressed in visible characters, you can convert the byte string to a visible string in hexadecimal format. For example, `(byte)1` is converted to `01`, and `(byte)27` is converted to `1B`. A binary array in Java format, such as `{(byte)1, (byte)27}`, is converted to `011b` or `011B`. Site monitoring is not case-sensitive to hexadecimal characters. Enter the string `"011B"` in the Response content match field and select Hexadecimal format for the Response content match format parameter.