All Products
Search
Document Center

Cloud Monitor:Create a multi-step detection task

Last Updated:Aug 21, 2025

Cloud Monitor simulates the access behavior of end users by using detection points (requesters) around the globe and obtains access data from these detection points to target URLs (monitored addresses). You can create a multi-step detection task to build single-step detection requests for multiple network protocols or target sites and combine them into a complex detection workflow to support various scenarios.

Prerequisites

One or more alert contacts and alert contact groups are created. For more information, see Create an alert contact or alert contact group.

Background information

  • For more information about activation and billing of the site monitoring feature, see Activate Network Analysis and Monitoring.

  • If your site is configured with high-level firewall policy settings or a whitelist, you may need to add the IP addresses of detection points to the whitelist so that the detection points can successfully access your site without being blocked by the firewall. For more information, see How do I configure a whitelist for a detection request if the detection request is mistakenly identified as an attack or a crawler?

  • Multi-step detection is suitable for the following scenarios:

    • Monitor business transactions at the API level and set alert rules.

    • Detect and diagnose application availability and performance at different network layers: Build a business test process that combines different network protocols such as DNS, PING, MTR, TCP, and HTTP. Each step serves a purpose, such as domain name resolution, network connectivity, port connectivity, and API availability. This provides more flexibility for network fault diagnosis.

Procedure

  1. Log on to the Cloud Monitor console.

  2. In the left-side navigation pane, choose Network Analysis and Monitoring > Site Monitoring.

  3. On the Monitoring Tasks tab, move the pointer over Create Task and click Multi-step Detection.

  4. In the Create Task panel, configure the following parameters.

    1. 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, underscores (_), Chinese characters, hyphens (-), and periods (.).

      Monitoring Frequency

      The frequency at which the site monitoring task sends detection requests to your site. For example, if you select 1 Minute, a detection point in a region sends a detection request to your site every minute.

      Specify Effective Period

      Turn on or off the Specify Effective Period switch based on your requirements. If you turn on the switch, you can specify a custom time range during which the multi-step detection task is effective.

    2. Define Steps

      Parameter

      Description

      Environment Variables

      Environment variables can be referenced in parameters of different test steps (using the placeholder {{$.<Variable name>}}). They can also be updated with values parsed from the results of a test step and then referenced in the next test step. For sensitive information such as API keys, you can select Encrypted Storage to mask the data.

      Note

      You can add multiple environment variables to store configuration information. You can use your custom environment variables when you add test steps.

      Multi-step Detection

      Add Step: In the Add Step panel, set the parameters for the test step. For more information about the parameters, see Monitor your sites from PCs over the Internet.

      Note

      When you configure the monitored address, you can reference custom environment variables using the format {{$.<Variable name>}}, for example, {{$.testurl}}.

      Add Wait Step: You can add multiple wait steps between test steps. Unit: seconds.

    3. Select Detection Points

      1. Set IP Protocol to the type of the IP address used by the site monitoring task. Valid values: IPv4, IPv6, and Automatic.

      2. Select detection points on the Recommend, All, or Custom tab as needed. If the default ones provided by Cloud Monitor do not meet your requirements, perform the following steps:

        1. Click Manage Custom Templates. In the panel that appears, click Create Template.

        2. In the dialog box that appears, set Template Name, select custom detection points, and click OK.

    4. Alert Rule

      Parameter

      Description

      Alerts

      • Recently Continuous: Select the number of consecutive cycles. Valid values: 1, 3, 5, 10, 15, 30, 60, 70, 90, 120, and 180.

      • Availability Rate:

        • Percentage of Available Detection Points: Percentage of available detection points = (Number of times that a domain name or IP address can be accessed properly within a monitoring period/Total number of detection requests) × 100%.

        • Number of Unavailable Detection Points: The number of times that the domain name or IP address of the site cannot be accessed as expected within a monitoring period.

        • Number of Available Detection Points: The number of times that the domain name or IP address of the site can be accessed as expected within a monitoring period.

        • Number of DNS Hijacking Detection Points: The number of detection points that encounter DNS hijacking. This metric is used to check whether DNS responses have been tampered with.

      • Response Time:

        • Average

        • Maximum Value

        • Minimum

        • Metric Value

      • Packet Loss Rate:

        • Ping Packet Loss Rate

      • Comparison operator: The operator that is used to compare the metric value with the alert threshold. Valid values:

        • >=

        • >

        • <=

        • <

        • =

        • !=

        • Compared With Yesterday Rise

        • Compared With Yesterday Decline

        • Compared With Last Week Rise

        • Compared With Last Week Decline

        • Compared With Last Period Rise

        • Compared With Last Period Decline

      • Alert level: Configure a custom threshold for each alert level. The following alert levels are available: Critical, Warning, and Info.

      Note

      For more information about how to configure alert rules, see the Configure Alert Rules step in the "Monitor your sites from PCs over the Internet" topic.

      Add Alert Rule

      You can add multiple alert rules.

      Alert Contact Group

      The alert contact groups to which alert notifications are sent. Select at least one alert contact group.

  5. Click OK.

What to do next

If the assertion failed error message appears when your site monitoring task is running, you can perform the following steps to view the cause of the assertion failure:

  1. On the Monitoring Tasks tab of the Site Monitoring Tasks page, click the name of the site monitoring task that you want to manage.

  2. On the Overview tab, navigate to the Error tab in the lower part of the page.

  3. Find the detection point that you want to troubleshoot, and click Details in the Actions column. In the panel that appears, view the cause of the assertion failure.

References