RUM Anomaly Detection¶

Used to monitor user access metric data within the workspace. Threshold ranges can be set, and the system automatically alerts when metrics exceed these thresholds.

Use Cases¶

Supports monitoring metric data for various types of applications including Web, Android, iOS, and Miniapp. For example, it can monitor the JS error rate for Web applications based on the city dimension.

Configuration¶

Detection Frequency¶

Refers to the execution frequency of the detection rule.

Detection Interval¶

Refers to the time range queried for the detection metrics. Affected by the detection frequency, the available detection interval options will differ.

Detection Metrics¶

Configure the detection metrics. You can set up monitoring for metric data of applications under a single application type within the current workspace, supporting a defined time range. For example: metric data for all applications under the Web type in the current workspace.

Web / Miniapp Metric Description¶

Android / IOS Metric Description¶

Trigger Conditions¶

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

Configure the trigger conditions and severity. When the query result contains multiple values, an event is triggered 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 the system to generate an event only 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 summary 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 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;

   • You can customize the number of detections. 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. Linked 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. Linked 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; when selecting this type of configuration strategy, the custom data gap time configuration is recommended to be >= detection interval time span. If the configured time <= detection interval time span, it may be possible to meet both data gap and abnormal conditions simultaneously. In this case, 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.