Create a Scheduled Dial Test Task

You can create a scheduled dial test task to conduct continuous active network dialtest of the monitoring targets, allowing you to understand the network quality of the monitored targets.

Steps

1. Log in to the UCloud Global Console ;

2. Navigate to All Products -> Monitoring & Operations -> Network Dial Test -> Scheduled Dial Test page, and click Create Dial Test Task ;

3. In the task creation interface, fill in the relevant information for the scheduled dial test task;

   Parameter Description

   • Basic Information

     ① Detection Mode

     ​ Single Target: Single task monitors a single dialtest target

     ​ Multiple Targets: Supports single task monitoring multiple dialtest targets simultaneously

     ② Dialtest Target: Enter the target address for the dial test.

     ?> For example: Domain name: console.ucloud-global.com / IP: 1.1.1.1

     ③ View Hierarchy: The system aggregates monitoring results according to the ISP, country, and province/city dimensions of the dialtest source, allowing you to drill down layer by layer in the selected hierarchy to view the network quality of different dimensions when checking the task monitoring results.

     ④ Probe Frequency: Supports dial test frequencies of 5 seconds, 15 seconds, 1 minute, 5 minutes, 10 minutes, 15 minutes, 30 minutes, and 1 hour or 2 hours. For example, selecting a frequency of 5 minutes means each dialtest point performs a dial test every 5 minutes.

     ⑤ Task End Time: Set the time to end the dialtest task. Provides quick time options, or you can customize the task end time.

   • Dial Test Configuration

     ① Select Dialtest Sources: Choose different regions or ISPs as dialtest sources as needed. You can also save the currently selected dialtest points as a dialtest source group for direct use when creating tasks in the future.

     ② Dial Test Parameter Configuration

     Parameter Name	Description	Default
     Protocol Type	Supports ICMP and TCP protocol types	ICMP
     TCP Ping Port	When Protocol Type is TCP, specify the port number	None
     Monitoring Timeout	Define the monitoring timeout limit, fillable range: 2 - 20 seconds	5
     Ping Packet Count	Enter the number of data packets sent per probe. Fillable range: 1-100	5
     Ping Packet Size	Size of the ICMP message for Ping dialtest , used to analyze the transmission differences with different message sizes (Note: This parameter is only available for ICMP protocol)	64
     DSCP	Located in the TOS byte of the IP packet header, using 6 bits used and 2 bits unused, distinguishes priorities by encoded value for service differentiation (Note: This parameter is only available for ICMP protocol)	0
     Allow Fragmentation	The DF (Don’t Fragment) flag in the IP packet header, when DF is 0, the router can segment the upper-layer packet (default is to allow segmentation); When DF is 1, the router cannot segment the packet. If an IP packet cannot be forwarded without segmentation (for instance, reaching the MTU limit), it will be discarded by the router. (Note: This parameter is only available for ICMP protocol)	Yes

     ?> Note: Ping interval (time interval for sending each packet) = probing frequency/Ping packet count.

   • Alarm Configuration

     ① Alarm Rules: You can configure alarm rules for monitoring indicators at different dimensions.

     ​ 1）Alarm Dimension: Choose the dimension corresponding to the alarm rule. Options include ISP, country, province/city, domain/IP, and single task.

     Alarm Dimension	Description
     Single Task	Indicates the aggregated result of all dialtest information from selected dialtest sources to all dialtest targets triggering an alarm rule on meeting conditions
     ISP	The system classifies all selected dialtest sources according to ISP dimension, aggregating data from the same ISP and triggering an alarm if the data meets the conditions
     Country	System classifies and aggregates selected dialtest sources by the country dimension, triggering an alarm if any country’s data meets the conditions
     Province/City	System classifies and aggregates selected dialtest sources by province/city, triggering an alarm if data for any province/city meets the conditions
     Domain/IP	Monitors all dialtest sources and targets for the task in a one-to-one relationship. If any source to target data meets alarm conditions, the alarm triggers

     ​ 2）Alarm Trigger Strategy: Set conditions to trigger the alarm.

     ​ 3）Monitoring Indicators: Provide packet loss rate and latency. At least one indicator must be selected.

     ​ 4）Threshold Type: Supports static and dynamic threshold types. (Note: Currently, only latency indicators support dynamic thresholds).

     ​ 5）Alarm Threshold and Levels: Set alarm thresholds and recovery thresholds corresponding to different alarm levels.

     ② Alarm Notification: Drop-down to select notification groups under the current project, supporting multiple groups. In case of an alarm, notifications will be sent according to the configured contacts and methods in the platform’s notification group.

     ③ Alarm Notification Strategy:

     ​ 1）Single Notification: Send an alarm notification only upon the initial alarm trigger.

     ​ 2）Repeat Notification: From the alarm trigger time until recovery, repeat sending notifications based on the set intervals.

   • MTR Configuration

     ① Threshold Trigger: If threshold trigger is enabled, set the packet loss rate threshold. If dialtest results meet the threshold, MTR will be triggered.

     ② Alarm Trigger: If alarm trigger is enabled, MTR will be triggered for dialtest sources-targets meeting alarm thresholds.

     !> Note: Executing MTR consumes a lot of resources. If numerous MTRs are triggered simultaneously for a task, the task scheduling system will randomly select some to execute.

   • Management Settings: Set the task name.