Monitor from public PC detection points - Cloud Monitor - Alibaba Cloud Documentation Center

Cloud Monitor uses site monitoring detection points to simulate end-user access behavior. This process collects access data from detection points in different regions for a target address (monitored address). You can use PC detection points to monitor a target site from the Alibaba Cloud network, carrier networks, or networks of cloud service providers outside China.

Background information

For more information about how to activate and use the site monitoring feature, see Activate Network Analysis and Monitoring.
If your site is configured with high-level firewall policy settings or a whitelist, you may need to add the IP addresses of detection points to the whitelist. This ensures that the detection points can access your site and are not blocked by the firewall. For more information, see How do I 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 2.0 console, and select a workspace. In the left navigation pane, choose Application Center > Synthetics Insights.
In the top navigation bar of the Synthetics Insights page, choose Timed Detection Tasks.
On the Timed Detection Tasks page, click Create Task.
On the Create Task page, select Service Availability Test.

Select a AddressType. The valid values are PC side (PC), Mobile (Mobile), and VPC Detection. Then, configure the monitoring task.

Select a Agreement

If you set Agreement to HTTP(S):

Parameter	Description
Task Name	Enter a name for the task.
Address	The target URL to monitor. Valid values: GET (default) POST HEAD
Advanced Settings	For more information about advanced settings for HTTP(S), see Advanced settings. Important The handshake protocols for TLS versions earlier than 1.2 have security vulnerabilities. Therefore, Cloud Monitor, in sync with major browsers, no longer supports server-side TLS versions earlier than 1.2. If a site monitoring task reports the error `tls: server selected unsupported protocol version 302` and you do not want to upgrade the server-side TLS protocol, you can select a compatible minimum TLS version on the Other tab in the Advanced Settings section.

If you set Task Type to PING:

Parameter	Description
Task Name	Enter a name for the task.
Address	The target domain name or IP address to monitor.
Protocol Type	The supported protocols are: icmp tcp udp
Number Of Ping Packets	The number of times to send a ping request. Default value: 10.

If you set Task Type to WEBSOCKET:
Parameter
Description
Task_Name
Enter a name for the task.
Address
The target IP address or domain name to monitor.
Advanced Settings
For more information about advanced settings, see Advanced settings.

If you set Task Type to DNS:

Parameter	Description
Task Name	Enter a name for the task.
Address	The target domain name to monitor.
Type	The type of the DNS query. Valid values: A (default) MX NS CNAME TXT ANY AAAA
DNS Access Protocol	The protocol for DNS access. Valid values: UDP (default) TCP TCP-TLS
DNS Server	The type of the DNS server. Valid values: System default DNS Carrier DNS of the detection point Custom DNS
Number of Retries after DNS Failure	Cloud Monitor verifies the domain name resolution result to check if it contains your expected domain names or IP addresses. The probe is successful if the expected list is a subset of the DNS list. Separate multiple domain names or IP addresses with commas (,).
Matching Rule	The matching rule for the domain names or IP addresses.
DNS Server Port	The port of the DNS server.

If you set Task Type to TCP or UDP:

Parameter	Description
Task Name	Enter a name for the task.
Address	The target IP address to monitor.
Advanced Settings	For more information about advanced settings for TCP or UDP, see Advanced settings.
Port	The port for the TCP or UDP protocol. Default value: 80.

If you set Task Type to SMTP or POP3:

Parameter	Description
Task Name	Enter a name for the task.
Address	The target domain name or IP address to monitor.
Port	The port for the SMTP or POP3 protocol. The default value for SMTP is 25. The default value for POP3 is 110.
Username	The username and password for the SMTP or POP3 server.
Password	The username and password for the SMTP or POP3 server.

If you set Task Type to FTP:

Parameter	Description
Name	Enter a name for the task.
Monitored Address	The target domain name or IP address to monitor.
Port	The port for the FTP protocol. Default value: 21.
Anonymous Logon	Anonymous logon (default) Requires identity verification If you select this option, you must set the username and password for the FTP server.
Username	The username and password for the FTP server.
Password	The username and password for the FTP server.

Available judgment: Cloud Monitor provides a default availability condition. If this condition does not meet your needs, you can add a new availability condition.
1. Click Add Condition Group.
2. Configure the availability conditions for the assertion.
  - Response Time(ms): Determines whether the response time meets expectations. The default value is less than 5000 ms.
  - Status Code: Determines whether the response status code meets expectations. The default status code is less than 400.
  - Header: Determines whether the fields in the response header meet expectations. You must specify the expected response header.
  - Body, XML Field of Body, JSON Field of Body: Determines whether the returned body content meets expectations using text character matching, XML parsing (XPath), or JSON parsing (JSON Path). For more information, see XPath Syntax and JSONPath Syntax.
3. Click Verify . The verification result is displayed on the right.
  - If the probe verification is successful, you can create the site monitoring task.
  - If the probe verification fails, check the error response and modify the task and assertion configurations.
Link tracing: Enable this feature as needed. This feature is available only for HTTP(S) tasks. For more information, see OpenTelemetry integration guide.
- Tracing Protocol: Optional protocols include OpenTelemetry W3C, Zipkin B3, and Jaeger.

Select Detection Points

Parameter

Description

Probe Node

Filter condition: The classification of detection points.

All nodes
- Node IP type: IPv4, IPv6, Automatic.
- Node type: IDC, LastMile.
- Region: China, Outside China.
Custom nodes: Select a custom detection point group.

Detection Interval: The monitoring interval (epoch). The valid values are 15 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, and 60 minutes. For example, if you select 1 minute, the detection points in each region monitor the target address once every minute. You can also customize the monitoring epoch to set a specific monitoring time.
Customize probe time range: Set the time range during which the monitoring task is active.

Click Create.

Advanced settings

The following tables describe the advanced settings for different monitoring types.

HTTP(S)

Tab	Parameter	Description
Request Parameters	HTTP Request Header	The format for an HTTP request header is `key1:value1`. Use the Enter key for a line break. Site monitoring pre-populates the request header 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` If your custom headers include any of the preceding headers, your settings overwrite the default ones. Note According to the HTTP protocol, site monitoring converts the keys in your request headers to the canonical format of Multipurpose Internet Mail Extensions (MIME) headers: The first letter and any letter that follows a hyphen (-) are converted to uppercase. 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 can be in the format of `key1=value1;key2=value2` or a JSON code snippet such as `{"test":"testValue"}`. Note This parameter is required when you set Request Method to POST.
	Unfollow Redirect	Specifies whether to follow redirects and perform another probe if a 301 or 302 status code is returned. By default, this option is not selected, which means redirects are followed.
	Certificate Verification	Specifies whether to enable certificate verification for the server on the client.
User Authentication	HTTP Authentication Username	Basic authentication over the HTTP protocol.
User Authentication	HTTP Authentication Password	Basic authentication over the HTTP protocol.
DNS Server	DNS Server	The IP address of the DNS server.
Others	Enable PROXY Protocol	Specifies whether to enable the proxy protocol. By default, this option is not selected, which means the protocol is not supported.
	Minimum TLS Version	The minimum TLS version that is compatible with Cloud Monitor. Valid values: `tlsv1.0` `tlsv1.1` `tlsv1.2` `tlsv1.3`
	Matching Response Mode	If the response content to match is not empty, site monitoring reads the first 64 KB of the HTTP server response body to find the specified content. Valid values: Alert if content is included Alert if content is not included Site monitoring determines whether to generate an alert based on the response matching method. The content to match must be in English.
	Match Response Content
	Acceptable Additional HTTP Status Codes	The HTTP status codes that are greater than or equal to 400. Separate multiple status codes with commas (,).

TCP or UDP

Parameter	Description
Request Format	This parameter is valid only when the request content is not empty. Valid values: Text Hexadecimal format
Request Content	Text A plain text string that consists of visible characters. Note Escape characters are not supported. For example, `\n` is not converted to a line break but is treated as two separate characters: `\` and `n`. 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 hexadecimal string. Rule: One byte is converted to a two-digit hexadecimal character. 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 for hexadecimal values. Enter the string `"011B"` in the Request content field and set Request content format to Hexadecimal format.
Matching Content Format	This parameter is valid only when the response content is not empty. Valid values: Text Hexadecimal format
Content Match	Text A plain text string that consists of visible characters. Note Escape characters are not supported. For example, `\n` is not converted to a line break but is treated as two separate characters: `\` and `n`. 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 hexadecimal string. Rule: One byte is converted to a two-digit hexadecimal character. 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 for hexadecimal values. Enter the string `"011B"` in the Request content field and set Request content format to Hexadecimal format.

Parameter	Description
Task_Name	Enter a name for the task.
Address	The target IP address or domain name to monitor.
Advanced Settings	For more information about advanced settings, see Advanced settings.