Cloud Monitor's site monitoring uses detection points to simulate end-user access and collect access data for your target URLs from various locations. Create a multi-step detection task to chain single-step probe requests across protocols or target sites into a monitoring workflow for a wide range of use cases.
Prerequisites
An alert contact and alert contact group are created. Create an alert contact or an alert contact group.
Background
-
To activate site monitoring and learn about billing, Activate Network Analysis and Monitoring.
-
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
-
Log on to the Cloud Monitor console.
-
In the left-side navigation pane, choose .
-
On the Monitoring Tasks tab, from the Create Task drop-down list, click Multi-step Detection.
-
In the Create Task panel, configure the following parameters.
-
Basic information:
Parameter
Description
DtsJobName
The task name. Must be 4 to 100 characters. Supports letters, digits, underscores (_), Chinese characters, hyphens (-), and periods (.).
Monitoring frequency
The monitoring interval. For example, 1 minute means each detection point probes the target every minute.
Specify effective period
The active time range for this task.
-
Define steps:
Parameter
Description
Environment variables
Reference variables in step parameters with the placeholder
{{$.. Parse results from previous steps to update variables for subsequent steps. For sensitive data such as API keys, select Encrypted Storage to mask the data.}} NoteYou can add multiple environment variables for use across request steps.
Multi-step detection
Add Step: Configure parameters for a single request step. Parameter details: Probe from PC detection points over the public network.
NoteIn the detection address, reference custom environment variables with the format
{{$.<variable_name>}}, for example,{{$.testurl}}.Add Wait Step: Add a wait period, in seconds, between single-step requests.
-
Select detection points:
Parameter
Description
IP protocol
The IP protocol for detection points. Valid values: IPv4, IPv6, and Automatic.
Select detection points from the Recommend, All, or Custom tabs. To create a custom template:
-
Click Manage Custom Templates. In the panel that appears, click Create Template.
-
In the dialog box, enter a Template Name, select the required detection points, and click OK.
-
-
Alert rule:
Parameter
Description
Alert
-
Recently continuous: Consecutive monitoring cycles before an alert triggers. Valid values: 1, 3, 5, 10, 15, 30, and 60.
-
Availability rate:
-
Percentage of available detection points: Percentage of successful probes per cycle. Formula: (successful probes / total probes) × 100%.
-
Number of unavailable detection points: Failed probes per monitoring cycle.
-
Number of available detection points: Successful probes per monitoring cycle.
-
Number of DNS hijacking detection points: Detection points that detected DNS hijacking.
-
-
Response time:
-
Average
-
Maximum
-
Minimum
-
Metric Value
-
-
Packet loss rate:
-
Ping packet loss rate
-
-
Comparison operator for metric values against the threshold. Valid values:
-
>=
-
>
-
<=
-
<
-
=
-
!=
-
Day-over-day increase
-
Day-over-day decrease
-
Week-over-week increase
-
Week-over-week decrease
-
Period-over-period increase
-
Period-over-period decrease
-
-
Alert level: Set a custom threshold for each severity: Critical, Warning, and Info.
NoteAlert rule details: Set alerts.
Add alert rule
You can add multiple alert rules.
Alert contact group
The contact group that receives alert notifications. Select at least one group.
-
-
-
Click OK.
Related operations
If a site monitoring task returns assertion failed, an assertion in your test failed. To identify the cause:
-
On the Site Monitoring page, go to the Monitoring Tasks tab and click the name of the target monitoring task.
-
On the Overview tab, find the detection results and click the Error tab.
-
Find the target detection point and click Details in the Actions column to view why the assertion failed.