The synthetic monitoring feature uses the globally distributed monitoring networks to view, perform, and download network synthetic monitoring on web applications such as websites and servers. This topic describes how to create a cloud dial-up network task.
- Log on to the ARMS console.
- In the left-side navigation pane, click Cloud Dial Test. On the Scheduled Dial Test page, click + Create Scheduled Task in the upper-right corner.
- In the Basic Information step, set the Task Name, Task Address, and Task Type parameters and click Next.
Parameter Description Job Name The name of the synthetic monitoring task. Task Address The URL of the web application on which you want to perform synthetic monitoring. addresses starting with
httpsare supported. addresses in the ip:port format are also supported.
Job Type Set Task Type to Network.
Network tasks support users to perform Ping monitoring, DNS monitoring, and Tracert monitoring on specified servers (IP addresses or domain names) to obtain link node network data, latency, packet loss, etc. during the monitoring process, and understand network link fluctuations in real time by analyzing various reports generated.
- In the Monitoring Points step, perform the following operations:
- Set the Adding Method parameter to Recommended Monitoring Point Group or Custom. Note The recommended monitoring point group includes monitoring points in major provinces and cities in China. The custom group includes all monitoring points supported by Alibaba Cloud Dial Test in the world.
- Select one or more monitoring point groups in the list on the left and click the icon. The monitoring points in the selected monitoring point groups are added to the Added list on the right.
- Click Next.
- Set the Adding Method parameter to Recommended Monitoring Point Group or Custom.
- In the Monitoring Parameters step, set the parameters and click Next.
Parameter Description IP Address Type The type of the IP address. Valid values:
Associated Items Filter Out Invalid IP Address Specifies whether to filter out the invalid IP address, which is 127.0.0.1. DNS Monitoring Monitoring Timeout The timeout period for monitoring, in seconds. Default value: 5. A timeout event is returned when the specified timeout period is reached. Query Mode The query method. Valid values:
- Recursion: queries the records on the common Domain Name System (DNS) servers.
- Iteration: queries the records on the authoritative DNS servers.
NS Server Enter the server address of the specified NS as required. The test will only use this server for resolution. DIG Specifies whether to display the data in the DIG format. DNS Server Type The type of the DNS server. Valid values:
Tracert Monitoring Monitoring Timeout The timeout period for monitoring, in seconds. Default value: 60. If the specified timeout period is reached, the server is inaccessible and the task is terminated. Maximum Hops The maximum number of hops allowed in route tracing. Default value: 20. If the number of hops exceeds the maximum value, the server is inaccessible. Ping Monitoring Protocol The type of the protocol. Valid values:
Monitoring Timeout The timeout period for monitoring, in seconds. Default value: 20. If the specified timeout period is reached, the ping operation fails. Execution Interval The intervals at which ping packets are sent. The next ping packet is sent at the specified intervals after the ping response is received for the previous packet. Packages Specifies the number of packets. Default value: 4. Split Package Specifies whether to split the ping packet. After you select the check box, you can customize the number and size of packets. Package Size Set the packet size. Hijacking parameters DNS hijacking whitelist When a domain name (for example, www.aliyun.com) is resolved, the resolved IP address or CNAME is not in the DNS hijacking whitelist, the user will fail to access or return a destination IP address that is not Aliyun. If the IP address or CNAME in the resolution result is in the DNS whitelist, it will be deemed that no DNS hijacking has occurred.
Domain Name: Matching Rule. Matching rules support IP, IP wildcard, subnet mask, and CNAME. You can enter multiple matching rules. Separate multiple matching rules with vertical bars (|). For example, www.aliyun.com:188.8.131.52|184.108.40.206 indicates that all IP addresses of the www.aliyun.com domain name except 220.127.116.11 and 18.104.22.168 are hijacked.
- In the Monitoring Cycle step, set the parameters and click Next.
Parameter Description Monitoring Frequency The intervals at which the synthetic monitoring task runs. Advanced Settings Start Execution Time The time to start running the synthetic monitoring task. This parameter is valid only when the synthetic monitoring task runs at long intervals. The value of this parameter cannot be greater than the value of the Monitoring Frequency parameter. Evenly Distribute Monitoring Samples Offset = Number of minutes in a cycle/Number of carriers. The earliest delivery time of each carrier is the value of the Start Execution Time parameter plus the offset.
Distributing monitoring samples evenly can be used to distribute dialing tasks to avoid an instantaneous increase in the traffic of the monitoring target website due to simultaneous dialing. We recommend that you select this parameter in scenarios with multiple monitoring points and high frequencies.
- In the Alert Parameter step, perform the following operations:
- Select an alert metric and turn on the switch on the right side of the alert metric.
- Configure the alert rule. For example,
packet loss rate alert: If the packet loss rate of a task is greater than 10%, an alert is triggered.
- Select a notification policy from the Notification policy drop-down list. You can click Create Notification from the drop-down list. In the Create Notification Policy panel, set Notification Name, Notification Person, and Notification Method to create a notification policy.
- Click Next.
- In the Preview & Publish step, confirm the parameters and click Complete. Then, the Scheduled dial test page appears.