All Products
Search
Document Center

CloudMonitor:Create an availability monitoring task

Last Updated:May 11, 2023

CloudMonitor provides the availability monitoring feature to help you check whether a local service or cloud server responds as expected. If a local service or cloud server times out or returns an error code, CloudMonitor sends an alert notification to you.

Background information

You can create availability monitoring tasks for the monitoring nodes and monitored objects. The monitoring nodes can be Elastic Compute Service (ECS) instances. The monitored objects can be URL or IP address, ApsaraDB RDS, or ApsaraDB for Redis.

Procedure

  1. Log on to the CloudMonitor console.
  2. In the left-side navigation pane, click Application Groups.

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

  4. In the left-side navigation pane of the page that appears, click Availability Monitoring.

  5. Click Create Availability Monitoring Task.

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

    Parameter

    Description

    Task Name

    The name of the availability monitoring task.

    Monitoring Nodes

    The IDs of the instances that you want to monitor. The instances IDs are all the ECS instance IDs in the application group.

    Detection Target

    The object that you want to monitor. Valid values:

    • URL or IP Address: the URL or IP address of the monitored object.

    • ApsaraDB RDS: Select this option only when you need to monitor ApsaraDB RDS instances in the application group.

    • ApsaraDB for Redis: Select this option only when you need to monitor ApsaraDB for Redis instances in the application group.

    Note

    If you set the Detection Target parameter to ApsaraDB RDS or ApsaraDB for Redis, a detection request is sent every second and the aggregated data is reported every minute.

    Detection Type

    The method that you want to use to monitor the object.

    If you set the Detection Target parameter to URL or IP Address, you can select one of the following methods:

    • HTTP(S): If you select this option, enter the URL of the object that you want to monitor.

    • TELNET: If you select this option, enter the IP address of the object that you want to monitor.

    • PING: If you select this option, enter the IP address of the object that you want to monitor.

    If you set the Detection Target parameter to ApsaraDB RDS or ApsaraDB for Redis, you can select one of the following methods:

    • TELNET: If you select this option, enter the instance ID and connection URL of the object that you want to monitor.

    • PING: If you select this option, enter the instance ID and connection URL of the object that you want to monitor.

    Request Method

    The request method. Valid values: HEAD, GET, and POST.

    Note

    This parameter is required if you set the Detection Target parameter to URL or IP Address and the Detection Type parameter to HTTP(S).

    Monitoring Frequency

    The interval at which detection requests are sent.

    Valid values: 15 Seconds, 30 Seconds, 1 Minute, 2 Minutes, 5 Minutes, 15 Minutes, 30 Minutes, and 60 Minutes. For example, if you select 1 Minute, CloudMonitor sends a detection request to the monitored object every minute.

    Note

    This parameter is required if you set the Detection Target parameter to URL or IP Address and the Detection Type parameter to HTTP(S).

    Headers

    The HTTP or HTTPS headers of detection requests for site monitoring.

    A header must be in the parameter1:value1 format.

    Separate multiple headers with commas (,).

    Note

    This parameter is required if you set the Detection Target parameter to URL or IP Address and the Detection Type parameter to HTTP(S).

    POST Content

    The content of POST requests for site monitoring.

    The content must be in the parameter1=value1&parameter2=value2 format and must be in English.

    Note

    This parameter is required if you set the Detection Target parameter to URL or IP Address, the Detection Type parameter to HTTP(S), and the Request Method parameter to POST.

    Match Response Content

    The response content that you want to match and the method used to match the response content.

    If you specify response content, the monitoring task checks whether the first 64 KB of the HTTP response body contains the response content that you specify. Valid values:

    • Generate Alerts If Response Contains

    • Generate Alerts If Response Does Not Contain

    Note

    This parameter is required if you set the Detection Target parameter to URL or IP Address and the Detection Type parameter to HTTP(S).

  7. Click Next.

  8. In the Configure Alert Rule step, configure parameters for the alert rule.

    Parameter

    Description

    Status Code

    If the status code reaches the specified value, an alert is triggered.

    An alert is triggered regardless of which value of the Status Code parameter or the Response Time parameter reaches the threshold. CloudMonitor sends alert notifications to the alert contact group of the application group.

    Response Time

    If the response time reaches the specified value, an alert is triggered.

    An alert is triggered regardless of which value of the Status Code parameter or the Response Time parameter reaches the threshold. CloudMonitor sends alert notifications to the alert contact group of the application group.

    Notification Methods

    The alert level and the methods that are used to send alert notifications. Valid values:

    Info (Email + Webhook)

    Alert Callback

    The callback URL that can be accessed over the Internet. CloudMonitor sends HTTP POST requests to push alert notifications to the specified URL. You can enter only an HTTP URL. For more information about how to configure alert callback, see Use the alert callback feature to send notifications about threshold-triggered alerts.

    Mute For

    The interval at which CloudMonitor resends alert notifications before the alert is cleared. Valid values: 5 Minutes, 15 Minutes, 30 Minutes, 60 Minutes, 3 Hours, 6 Hours, 12 Hours, and 24 Hours.

    If the threshold value is exceeded, CloudMonitor sends an alert notification. If the threshold value is exceeded again within the mute period, CloudMonitor does not resend an alert notification. If the alert is not cleared when the mute period elapses, CloudMonitor resends an alert notification.

    Effective Period

    The validity period of the alert rule. CloudMonitor sends alert notifications only within the validity period of the alert rule and records events when the validity period expires.

  9. Click OK.