Cloud Monitor:Create an availability monitoring task

Procedure

1. Log on to the Cloud Monitor console.

2. In the left-side navigation pane, choose Cloud Resource Monitoring > Application Groups.

3. On the Application Groups tab, click the name of the target application group.

4. In the left-side navigation pane of the target application group, click Availability Monitoring.

5. Click Create Availability Monitoring Task.

6. In the Create/Modify Availability Monitoring Task panel, configure the task parameters.

   Parameter	Description
   DtsJobName	The name of the availability monitoring task.
   Monitoring nodes	The ECS instances that send the detection requests. Note Monitoring nodes are the ECS instances in the current application group.
   Monitored object	The target of the monitoring task. Valid values: URL or IP address: Enter the target URL or IP address. ApsaraDB RDS: An ApsaraDB RDS instance in the current application group. Tair: A Tair instance in the current application group. Note If you set Monitored object to ApsaraDB RDS or Tair, detection requests are sent once per second, and aggregated data is reported once per minute.
   Detection type	The detection protocol. If you set Monitored object to URL or IP address, the following detection types are available: HTTP(S): Enter the target URL. TELNET: Enter the target IP address. PING: Enter the target IP address. If you set Monitored object to ApsaraDB RDS or Tair, the following detection types are available: TELNET: Select the instance ID and connection address to monitor. PING: Select the instance ID and connection address to monitor.
   Request method	The HTTP request method. Valid values: HEAD, GET, and POST. Note Required when Monitored object is URL or IP address and Detection type is HTTP(S).
   Monitoring frequency	The detection request interval. Valid values: 15 seconds, 30 seconds, 1 minute, 2 minutes, 5 minutes, 15 minutes, 30 minutes, and 60 minutes. Note Required when Monitored object is URL or IP address and Detection type is HTTP(S).
   Headers	HTTP or HTTPS headers for detection requests. The header format is parameter1:value1. Separate multiple headers with a comma (,). Note Required when Monitored object is URL or IP address and Detection type is HTTP(S).
   POST content	The POST request body. Format: parameter1=value1&parameter2=value2. Only English characters are supported. Note Required when Monitored object is URL or IP address, Detection type is HTTP(S), and Request method is POST.
   Match response content	Response validation criteria. The task checks the first 64 KB of the HTTP response body for the specified content. Matching methods: Generate alert if response contains Generate alert if response does not contain Note Required when Monitored object is URL or IP address and Detection type is HTTP(S).

7. Click Next.

8. On the Alert settings page, configure alert parameters.

   Parameter	Description
   Status code	The status code conditions that trigger an alert. An alert is sent to the application group's contact group when either the status code or response time reaches the threshold.
   Response time	Response time threshold (in milliseconds) that triggers alerts. An alert is sent to the application group's contact group when either the status code or response time reaches the threshold.
   Alert level	Alert severity and notification channels: Info (Email + Webhook)
   Alert callback	A public URL that receives alert notifications via POST requests. Only HTTP is supported. Use threshold-based alert callbacks.
   Mute period	Interval before resending an alert for an unresolved issue. Valid values: 5 minutes, 15 minutes, 30 minutes, 60 minutes, 3 hours, 6 hours, 12 hours, and 24 hours. After an alert triggers, no repeat notifications are sent during the mute period. If the issue persists beyond this period, a new alert is sent.
   Effective period	The time range when the alert rule is active. Alerts outside this range are logged but do not trigger notifications.
   Log Service	When Log Service is enabled, alerts are written to a Log Service Logstore. Configure the Region, ProjectName, and Logstore. Use LoongCollector to collect and analyze text logs on ECS instances.

9. Click OK.