User Access Metrics Monitoring¶

This feature monitors metrics related to user access within the workspace. Threshold ranges can be set, and when metrics exceed these thresholds, the system will automatically trigger alerts. Additionally, it supports configuring alert rules for individual metrics and allows customization of alert severity levels.

Use Cases¶

It supports monitoring metrics data for various types of applications, including Web, Android, iOS, and Miniapp. For example, you can monitor JS error rates based on city dimensions for web applications.

Detection Configuration¶

Detection Frequency¶

The execution frequency of detection rules; the default is 5 minutes.

Detection Interval¶

The time range for querying detection metrics. Depending on the detection frequency, different intervals are available.

Detection Metrics¶

Set the metrics for detecting data. It supports setting all or single application metrics under a specific application type within the current workspace for a certain time range. For example: all application metrics data under the Web type in the current workspace.

Web / Miniapp Metrics Description¶

Android / iOS Metrics Description

Trigger Conditions¶

Set the trigger conditions for alert levels: You can configure any one of the critical, major, minor, or normal trigger conditions.

Configure the trigger conditions and severity level. When the query results contain multiple values, if any value meets the trigger condition, an event is generated.

For more details, refer to Event Level Description.

If Continuous Trigger Judgment is enabled, you can configure the number of consecutive times the trigger condition must be met before another event is generated. The maximum limit is 10 times.

Alert Levels

1. Critical (Red), Major (Orange), Minor (Yellow): Based on the configured condition operators.

For more details, refer to Operator Description.

1. Normal (Green): Based on the configured detection count, as follows:

2. Each execution of a detection task counts as 1 detection, e.g., [Detection Frequency = 5 minutes], then 1 detection = 5 minutes;

3. You can customize the detection count, e.g., [Detection Frequency = 5 minutes], then 3 detections = 15 minutes.

Level

Description

Normal

After the detection rule takes effect, if critical, major, or minor events occur, and within the configured custom detection count, the data returns to normal, a recovery alert event is generated. Recovery alert events are not subject to Alert Mute restrictions. If no recovery alert event detection count is set, the alert event will not recover and will remain in the Events > Unrecovered Events List.

Data Discontinuity¶

For data discontinuity states, seven strategies can be configured.

1. Linked to the detection interval time range, judge the query results of the most recent minutes for the detection metrics, do not trigger events;

2. Linked to the detection interval time range, judge the query results of the most recent minutes for the detection metrics, treat query results as 0; at this point, the query results will be compared against the threshold configured in the Trigger Conditions to determine if an anomaly event should be triggered.

3. Custom fill for the detection interval value, trigger data discontinuity events, trigger critical events, trigger major events, trigger minor events, and trigger recovery events; when choosing this type of configuration strategy, it is recommended that the custom data discontinuity time be >= detection interval time. If the configured time <= detection interval time, there may be simultaneous satisfaction of data discontinuity and anomaly conditions, in which case only the data discontinuity handling result will apply.

Information Generation¶

Enabling this option will generate "Information" events for detection results that do not match the above trigger conditions and write them into the log.

Note: If trigger conditions, data discontinuity, and information generation are configured simultaneously, the following priority applies: data discontinuity > trigger conditions > information event generation.