If an existing site monitoring task cannot meet your business requirements, you can modify the task in the CloudMonitor console.

Procedure

  1. Log on to the CloudMonitor console.
  2. In the left-side navigation pane, choose Network Analysis and Monitoring > Site Monitoring (Timing Dial Test).
  3. On the Monitoring Tasks tab, find the site monitoring task that you want to modify, and click Edit in the Actions column.
  4. On the Modify Task page, modify the parameters of the task.
    • Basic Information
      Parameter Description
      Task Name The name of the site monitoring task. The name must be 4 to 100 characters in length, and can contain letters, digits, and underscores (_).
      Monitored Address The address of the site that you want to monitor.
      Frequency The frequency at which the site monitoring task sends detection requests to the site that you want to monitor. Valid values: 15 Seconds, 1 Minutes, 5 Minutes, 15 Minutes, 30 Minutes, and 60 Minutes. For example, if you select 1 Minutes, a detection point in a region sends a detection request to the site that you want to monitor every minute.
      Advanced Settings The advanced settings for the selected protocol. For more information about the advanced settings that are supported by different protocols, see Description.
    • Assertion definition
      If you set the Task Type to HTTP(S), you can use the assertion feature to set conditions and check whether a detection point meets your expectations based on the verification result. You can configure multiple assertions by specifying conditions. A detection point is available only if it meets all the specified conditions.
      Note For HTTP detections, if you do not set the status code assertion, status codes less than 400 are available by default.
      CloudMonitor provides an available condition by default. If the default condition cannot meet your business requirements, perform the following steps to add conditions:
      1. Click Add Condition Group.
      2. Configure the condition of the assertion.
        • Response time (ms): checks whether the response time meets expectations. Default setting: less than 1,000 ms.
        • Status code: checks whether the response status code meets expectations. Default status code: less than 400.
        • Header: checks whether the fields in the response header meet expectations. You must configure a custom condition for the response header assertion.
        • Body, xml field of body, and json field of body: checks whether the content in the response body meets expectations by using text matching, XML parsing (XPath), and JSON parsing (JSONPath). For more information, see XPath Syntax and JSONPath Syntax.
      3. Click Verify.
        You can view the verification result on the right side of the page.
        • If the verification result is Successful, you can create a site monitoring task as expected.
        • If the verification result is Failed, you can perform network diagnostics on the corresponding detection point.
    • Select Detection Points
      Parameter Description
      IP Protocol The type of the IP address that is used by the site monitoring task. Valid values: IPV4 and IPV6.
      Select detection points The default detection points and custom detection points that are used for site monitoring.
      If the default detection points cannot meet your business requirements, perform the following steps to add custom detection points.
      1. Click the Modify icon next to Select Custom Detection Points.
      2. Click Create Template.
      3. Enter a custom template name in the Template Name field and select custom detection points that you want to use.
      4. Click OK.
      5. Click OK.
    • Configure Alert Rules
      CloudMonitor provides an alert rule by default. If the default rule cannot meet your business requirements, perform the following steps to add an alert rule:
      1. Click Add Rule Description.
      2. In the panel that appears, configure parameters for the alert rule. The following table describes the parameters.
        Parameter Description
        Rule Name Enter a name for the alert rule.
        Metric Name The name of the metric that is used by the alert rule. Valid values:
        • Percentage of available probe points

          Percentage of available detection points = Number of available detection points /Total number of detection requests × 100%.

        • Number of unavailable probe points

          This metric specifies the number of times that the domain name or IP address of the site cannot be accessed as expected in a monitoring period.

        • Number of available probe points

          This metric specifies the number of times that the domain name or IP address of the site can be accessed as expected in a monitoring period.

        • Any Status Code (Independent Alert)

          If the status code that is returned by one of the detection points meets the specified condition, an alert is triggered.

        • All Status Code (Combined Alert)

          If the status codes that are returned by all detection points meet the specified condition, an alert is triggered.

        • ResponseTime
        Comparison The comparison operator that is used in the alert rule. Valid values:
        • >=
        • >
        • <=
        • <
        • =
        • !=
        • Compare With Yesterday Rise
        • Compare With Yesterday Decline
        • Compare With Last Week Rise
        • Compare With Last Week Decline
        • Compare With Last Period Rise
        • Compare With Last Period Decline
        Threshold and Alert Level The alert level and the corresponding threshold.

        Valid values of the alert level: Critical, Warn, and Info.

        Valid values of the number of consecutive periods in which the metric value crosses the threshold before an alert is triggered: 1, 2, 3, 4, 5, 10, 15, and 20.

        Tag The tags of the alert rule.
      3. Click OK.
    • Select Alert Contact Groups
      Parameter Description
      Select alert contact groups The alert contact groups to which alert notifications are sent.

      The alert notifications are sent to the alert contacts that belong to the selected alert contact groups. An alert contact group can contain one or more alert contacts.

      For information about how to create an alert contact and an alert contact group, see Create an alert contact or alert contact group.

      Mute For The interval at which CloudMonitor sends alert notifications until the alert that is triggered based on the alert rule 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 after the mute period ends, CloudMonitor resends an alert notification.

      Note You can click Advanced Settings to configure this parameter.
      Effective Period The period during which the alert rule is effective. CloudMonitor monitors the specified resources based on the alert rule only within the specified period.
      Note You can click Advanced Settings to configure this parameter.
      Alert Callback The 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.
      Note You can click Advanced Settings to configure this parameter.
  5. Click Modify.

Description

The following tables describe the advanced settings for different protocols.
  • HTTP or HTTPS
    Parameter Setting method Required Description
    Monitor Address URL Yes None.
    Request Method Option button Yes
    The HTTP request method. Valid values:
    • GET (default value)
    • POST
    • HEAD
    HTTP Request Header Multiple lines of text No
    An HTTP header is a key-value pair in which the key and value are separated by a colon (:). Each HTTP header occupies a line. Site monitoring adds the following preset headers to the request:
    • Host:${Domain name in the monitored address}
    • Pragma:no-cache
    • Cache-Control:no-cache
    • User-Agent:Chrome/57
    • Accept: */*

    If the request body is a form, the request also contains the following header:

    Content-Type: application/x-www-form-urlencoded;charset=UTF-8

    If your request contains one or more of the preceding headers, the headers are overwritten by your settings.

    Note Site monitoring converts the keys that you specify in the request headers to the canonical format of MIME headers based on the following rules of the HTTP protocol:
    • The first letter and the letter that follows a hyphen (-) are converted to uppercase letters. For example, accept-encoding is converted to Accept-Encoding.
    • If a key contains a space or invalid characters, the key remains unchanged.
    Cookie Cookie text No The HTTP cookie.
    Request content Form data or JSON objects No The request content can contain multiple key-value pairs in the key1=value1;key2=value2 format or a JSON string in the {"test":"testValue"} format.
    Note This parameter is required if you set the Request Method parameter to POST.
    Match response method Option button Yes
    If you specify the response content that you want to match, site monitoring checks whether the first 64 KB of the response body contains the response content that you specify. Valid values:
    • Generate Alerts If Response Contains
    • Generate Alerts If Response Does Not Contain

    Site monitoring determines whether to generate an alert based on the mode in which the response is matched.

    The matching content must be in English.

    Match Response Content Text No
    Acceptable additional HTTP status codes Text No An HTTP status code that is greater than or equal to 400. Separate multiple status codes with commas (,).
    HTTP Authentication Username Username No The username and password that are used for basic HTTP authentication.
    HTTP Authentication Password Password No
    Certificate Verification Check box No Specifies whether server name indication (SNI) is supported. By default, the check box is cleared. This indicates that SNI is not supported.
    Unfollow Redirect Check box No Specifies whether to follow redirects if the status code 301 or 302 is returned. By default, the check box is cleared. This indicates that redirects are followed.
    Enable PROXY Protocol Check box No By default, the check box is cleared. This indicates that the proxy protocol is not supported.
    DNS server Domain name or IP address of the server No The DNS server of IP address.
  • PING
    Parameter Setting method Required Description
    Monitor Address URL Yes None.
    Number of ping packets Positive integer Yes The number of times that the site is pinged. Default value: 10.
  • TCP or UDP
    Parameter Setting method Required Description
    Monitor Address URL Yes None.
    Port Positive integer Yes The TCP or UDP port.
    Request Format Option button Yes This parameter takes effect only if you set the Request content parameter. Valid values:
    • Text
    • Hexadecimal Format
    Request content Common text or hexadecimal format No
    • Common text
      Common text refers to strings that consist of printable characters.
      Note Common text does not support escaping. For example, \n is considered as two characters (\ and n) rather than the newline character.
    • Hexadecimal format

      If the request content is a byte string that cannot be presented in printable characters, you can convert the byte string to a hexadecimal string that consists of printable characters. Conversion rules: A byte is converted to two hexadecimal characters. For example, (byte)1 is converted to 01, and (byte)27 is converted to 1B.

      Binary array in the Java format: {(byte)1, (byte)27} is converted to 011b or 011B. Hexadecimal characters are not case-sensitive in site monitoring. Enter "011B" in the Request content field and set the Request Format parameter to Hexadecimal Format.

    Matching Content Format Option button Yes This parameter takes effect only if you set the Content Match parameter. Valid values:
    • Text
    • Hexadecimal Format
    Content Match Common text or hexadecimal format No
    • Common text
      Common text refers to strings that consist of printable characters.
      Note Common text does not support escaping. For example, \n is considered as two characters (\ and n) rather than the newline character.
    • Hexadecimal format

      If the request content is a byte string that cannot be presented in printable characters, you can convert the byte string to a hexadecimal string that consists of printable characters. Conversion rules: A byte is converted to two hexadecimal characters. For example, (byte)1 is converted to 01, and (byte)27 is converted to 1B.

      Binary array in the Java format: {(byte)1, (byte)27} is converted to 011b or 011B. Hexadecimal characters are not case-sensitive in site monitoring. Enter "011B" in the Request content field and set the Request Format parameter to Hexadecimal Format.

  • DNS
    Parameter Setting method Required Description
    Monitor Address URL Yes None.
    Type Option button Yes The type of DNS records that you want to query.

    Valid values: A, MX, NS, CNAME, TXT, ANY, and AAA. Default value: A.

    DNS Access Protocol Option button Yes The transport layer protocol used by DNS.

    Valid values: udp, tcp, and tcp-tls.

    DNS Server Domain name or IP address of the server No Valid values:
    • System default DNS
    • The operator DNS corresponding to the detection point
    • Custom DNS
    Number of retries after DNS failure. An integer greater than or equal to 0 No The number of retries after a DNS detection fails.
    Expected resolution result Multiple lines of text No

    CloudMonitor checks whether the DNS resolution result contains the expected domain names or IP addresses. If the list of expected values is a subset of the list of DNS results, the detection is considered successful.

    Separate multiple domain names or IP addresses with commas (,).

    Match Rule An option from the drop-down list No The matching rule for the domain name or IP address.
  • SMTP
    Parameter Setting method Required Description
    Monitor Address URL Yes None.
    Port Positive integer Yes The SMTP port.
    Username Text Yes

    The username and password that are used for PLAIN authentication.

    Make sure that the username and password that you specify are correct. Site monitoring sends detection requests based on the frequency that you specify. If the username or password is wrong, your account may be blocked by the destination service due to frequent logon failures.

    Password Text Yes
    Secure Connection Option button Yes Specifies whether to use Secure Sockets Layer (SSL) for the SMTP connection. Valid values:
    • Use
    • Not Use
  • POP3
    Parameter Setting method Required Description
    Monitor Address URL Yes None.
    Port Positive integer Yes The POP3 port.
    Username Text Yes

    The username and password that are used for authentication.

    Make sure that the username and password that you specify are correct. Site monitoring sends detection requests based on the frequency that you specify. If the username or password is wrong, your account may be blocked by the destination service due to frequent logon failures.

    Password Text Yes
    Secure Connection Option button Yes Specifies whether to use SSL for the POP3 connection. Valid values:
    • Use
    • Not Use
  • FTP
    Parameter Setting method Required Description
    Monitor Address URL Yes Example: ftp://smtp.aliyun.com.
    Port Positive integer Yes The FTP port.
    Anonymous Logon Option button Yes
    • Anonymous Logon (default value)
    • Authentication Required

      If you select the Authentication Required option, you must specify the username and password of the FTP server.

    Username Text Yes

    The username and password of the FTP server.

    Password Text Yes