All Products
Search

This Product

    Cloud Monitor:Business Flow Detection

    Document Center

    Cloud Monitor:Business Flow Detection

    Last Updated:Jun 22, 2026

    Cloud Monitor uses site monitoring detection points to simulate end-user access and collect access data from different regions. You can combine single-step requests across multiple network protocols or target sites into a multi-step detection task for complex detection workflows.

    Background

    • If your site has a firewall or access restrictions, add detection point IP addresses to the allowlist. What to do if a detection request is mistaken for an attack or a web crawler?

    • Use cases:

      • Monitor business-critical API workflows and configure alert rules.

      • Perform layered network diagnostics by combining protocols such as DNS, PING, MTR, TCP, and HTTP to diagnose availability and performance from DNS resolution through network connectivity to port connectivity and API availability.

    Procedure

    1. Log on to the Cloud Monitor 2.0 console, and select a workspace. In the left navigation pane, choose Application Center > Synthetics Insights.

    2. On the Synthetic Monitoring page, click Scheduled Probe Task in the top navigation bar.

    3. On the Scheduled Probe Task page, click Create Task.

    4. On the Create Task page, select Workflow Test and click Next.

    5. Configure the task.

      1. Basic information:

        Parameter

        Description

        Task Name

        Enter a name for 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 interval at which the task runs. For example, if you select 1 minute, detection points in each region monitor the target address once every minute.

        Specify Effective Period

        Optional. Enable this to specify a custom effective period for the task.

      2. Define Steps:

        Parameter

        Description

        Environmental Variable

        Use environment variables across test steps with the {{$.<variable_name>}} placeholder. You can parse a step's response to update a variable for subsequent steps. For sensitive data such as API keys, select Encrypted Storage to mask the data.

        Note

        Add environment variables to store configurations for use in single-step requests.

        Multi-step Detection

        Add Step: In the Add Request dialog box, configure the parameters for the single-step request. For more information about the parameters, see Detection from PC detection points over the Internet.

        Note

        When you set a probe address, you can reference a custom environment variable. The format is {{$.<variable name>}}. For example: {{$.testurl}}.

        Add Wait Step: Add one or more wait steps (in seconds) between single-step requests.

      3. Select Detection Points:

        Parameter

        Description

        IP Protocol

        The category of detection points for the task.

        • All Nodes

          • node IP type: IPv4, IPv6, or Automatic.

          • node type: IDC or LastMile.

          • region: Chinese mainland or Outside the Chinese mainland.

        • Custom Nodes: Select a custom detection point group.

      4. Monitoring Frequency: The monitoring interval. Valid values: 15 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, and 60 minutes. For example, if you select 1 minute, each region's detection points probe the target address once per minute. You can also customize the interval and set a precise monitoring time.

      5. Specify Effective Period: Set the effective period for the probe task.

    6. Click Finish.

    Related documents