Application Performance Metrics Detection¶

Used to monitor key metrics data of APM within the workspace. The system counts the number of qualified traces within a specified time period, and triggers an anomaly event when it exceeds the custom threshold.

Detection Configuration¶

Detection Frequency¶

The execution frequency of the detection rule.

Detection Interval¶

The time range for querying metrics each time the task is executed. The available detection intervals vary depending on the detection frequency.

Detection Metrics¶

Set the metrics for detection data, which can be used to configure the metrics data of services within the workspace for a specified time range.

Trigger Conditions¶

Set the trigger conditions for alert levels: You can configure any one of the emergency, important, warning, and normal trigger conditions.

Configure the trigger conditions and severity. When the query result has multiple values, any value that meets the trigger condition will generate an event.

For more details, refer to Event Level Description.

Continuous Trigger Judgment¶

If continuous trigger judgment is enabled, it means that after the trigger condition is judged to be effective multiple times in a row, an event will be triggered again. The maximum limit is 10 times.

Bulk Alert Protection¶

Enabled by default.

When the number of alerts generated by a single detection exceeds the preset threshold, the system will automatically switch to the status summary strategy: instead of processing each alert object individually, it will generate a small number of summary alerts based on the event status and push them.

This ensures the timeliness of notifications and significantly reduces alert noise, avoiding the risk of timeout due to processing too many alerts.

Alert Levels¶

1. Emergency (Red), Important (Orange), Warning (Yellow) Alert Levels: Based on the configured condition judgment operators.

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

   • Each execution of a detection task counts as 1 detection, e.g., detection frequency = 5 minutes, then 1 detection = 5 minutes;

   • The number of detections can be customized, e.g., detection frequency = 5 minutes, then 3 detections = 15 minutes.

   Level

   Description

   Normal

   After the detection rule takes effect, if emergency, important, or warning anomaly events are generated, and the data detection results return to normal within the configured custom number of detections, a recovery alert event will be generated. Recovery alert events are not restricted by alert silence. If the number of detections for recovery alert events is not set, the alert event will not recover and will always appear in the Events > Unrecovered Events List.

Data Gap¶

For data gap status, seven strategies can be configured.

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

2. Link the detection interval time range, judge the query result of the detection metrics for the most recent minutes, consider 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 anomaly event.

3. Custom fill the detection interval value, trigger data gap event, trigger emergency event, trigger important event, trigger warning event, and trigger recovery event; for this type of configuration strategy, it is recommended to configure the custom data gap time >= detection interval time interval. If the configured time <= detection interval time interval, there may be situations where both data gap and anomaly conditions are met, in which 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 the above trigger conditions.

Other Configurations¶

For more details, refer to Rule Configuration.