Synthetic Testing Anomaly Detection¶

Used to monitor Synthetic Tests data within the workspace. You can set threshold ranges for the specified data volume generated by testing tasks over a period of time. Once the data volume reaches these thresholds, the system will trigger alerts. Furthermore, you can customize alert levels, enabling the triggering of corresponding level alert events when the specified data volume reaches different threshold ranges.

Use Cases¶

Supports monitoring data volume generated from HTTP, TCP, ICMP, WEBSOCKET, and Multistep Tests. For example, monitoring the unavailability of a URL deployed in a production environment.

Configuration¶

Detection Frequency¶

Refers to the execution frequency of the detection rule.

Detection Interval¶

Refers to the time range for querying detection metrics. The available detection interval options vary depending on the detection frequency.

Detection Metrics: Set the metrics for the detection data. Supports setting the data volume of specified data generated by all or a single testing task within the current workspace as the detection metric.

Trigger Conditions¶

Set the trigger conditions for alert levels: You can arbitrarily configure one of the trigger conditions: Critical, Important, Warning, or Normal.

Configure trigger conditions and severity. When the query result contains multiple values, an event is generated if any value satisfies the trigger condition.

For more details, refer to Event Level Description.

Consecutive Trigger Judgment¶

If Consecutive Trigger Judgment is enabled, you can configure that an event is triggered again after the trigger condition is met for a consecutive number of times. The maximum limit is 10 times.

Bulk Alert Protection¶

Enabled by default.

When the number of alerts generated in a single detection exceeds a preset threshold, the system automatically switches to a status aggregation strategy: instead of processing alert objects individually, it generates a small number of summary alerts based on event status and pushes them.

This ensures the timeliness of notifications while significantly reducing alert noise and avoiding timeout risks caused by processing too many alerts.

Alert Level¶

1. Alert Level Critical (red), Important (orange), Warning (yellow);

2. Alert Level Normal (green): Based on the configured number of detections, explained as follows:

   • Each execution of a detection task counts as 1 detection. For example, if Detection Frequency = 5 minutes, then 1 detection = 5 minutes;

   • The number of detections can be customized. For example, if Detection Frequency = 5 minutes, then 3 detections = 15 minutes.

   Level

   Description

   Normal

   After the detection rule takes effect, if an Critical, Important, or Warning abnormal event occurs, and the data detection result returns to normal within the configured custom number of detections, a recovery alert event is generated. ❗️ Recovery alert events are not subject to Alert Silence restrictions. If the number of detections for recovery alert events is not set, the alert event will not recover and will remain in the Events > Unrecovered Events List.

Data Gap¶

Seven strategies can be configured for data gap status.

1. Link with the detection interval time range, judge the query result of the detection metric for the most recent minutes, do not trigger an event;

2. Link with the detection interval time range, judge the query result of the detection metric for the most recent minutes, treat the query result as 0; At this time, the query result will be re-compared with the threshold configured in the Trigger Conditions above to determine whether to trigger an abnormal event.

3. Custom fill the detection interval value, trigger data gap event, trigger critical event, trigger important event, trigger warning event, and trigger recovery event; For this type of configuration strategy, the recommended custom data gap time configuration is >= detection interval time span. If the configured time <= detection interval time span, situations where both data gap and abnormal conditions are met may occur. In such cases, only the data gap processing result will be applied.

Information Generation¶

Enable this option to generate "Information" events for detection results that do not match any of the above trigger conditions.

Other Configuration¶

For more details, refer to Rule Configuration.