Process Anomaly Detection¶

Used to monitor process data within the workspace, supports configuring alert trigger conditions for one or more field types in process data.

Detection Configuration¶

Detection Frequency¶

Refers to the execution frequency of the detection rule.

Detection Interval¶

Refers to the time range for querying detection metrics. Affected by the detection frequency, the available detection intervals may vary.

Detection Metrics¶

Set the metric data to be detected. Supports setting the number of occurrences of one or more field type keywords in process data within the current workspace over a certain time range.

Trigger Conditions¶

Set the trigger conditions for alert severity levels: You can configure any one of the trigger conditions for Critical, Major, Warning, or Normal.

Configure the trigger conditions and severity. When the query result contains multiple values, an event is generated if any value meets 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 generated only after the trigger condition is met for a consecutive number of times. The maximum 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 each alert object 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 Severity¶

1. Alert Severity Critical (red), Major (orange), Warning (yellow);

2. Alert Severity 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, Major, 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 a data gap event, trigger a Critical event, trigger a Major event, trigger a Warning event, and trigger a recovery event; for this type of configuration strategy, the recommended custom data gap time configuration is >= detection interval time. If the configured time is <= the detection interval time, situations where both data gap and anomaly 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 meet any of the above trigger conditions and write them.

Other Configurations¶

For more details, refer to Rule Configuration.