Alert Aggregation Notification Templates¶
Title¶
You have {N} {{level}} alert notifications
Content¶
No Aggregation¶
You have N new Guance alerts
Item 1 / 2:
Title
Content
Go to Workspace to View
Go to Workspace for AI Intelligent Analysis
Item 2 / 2:
Title
Content
Go to Workspace to View
Go to Workspace for AI Intelligent Analysis
- Go to Workspace to View: Jumps to the Event Explorer to view the current event (filter condition:
df_event_id)
Diagram:
Rule Aggregation¶
All¶
Related Events: 123
Aggregation Period: 2023/11/20 10:00 ~ 2023/11/20 10:05
Related Detection Rules:
- {{Event Title}} >>View
- View: Jumps to the Explorer to view all events generated by the current monitor during the aggregation period (filter condition:
df_monitor_checker_id)
Diagram:
Detection Rule - Monitor¶
Detection Type: Monitor
Detection Rule Name: {{Host}} CPU exceeds {Result}%
Detection Rule ID: rule_cdbkjcbsdjcb1234445455
Related Events: 123
Aggregation Period: 2023/11/20 10:00 ~ 2023/11/20 10:05
Go to Workspace to View
- View: Jumps to the Explorer to view events related to the current monitor (filter condition:
df_monitor_checker_id)
Detection Rule - Intelligent Inspection¶
Detection Type: Intelligent Inspection
Detection Rule Name: {{Host}} CPU exceeds {Result}%
Detection Rule ID: rule_cdbkjcbsdjcb1234445455
Related Events: 123
Aggregation Period: 2023/11/20 10:00 ~ 2023/11/20 10:05
Go to Workspace to View
Go to Workspace for AI Intelligent Analysis
- View: Jumps to the Explorer to view events related to the current Intelligent Inspection rule (filter condition:
df_monitor_checker_id)
Detection Rule - SLO¶
Detection Type: SLO
Detection Rule Name: {{Host}} CPU exceeds {Result}%
Detection Rule ID: rule_cdbkjcbsdjcb1234445455
Related Events: 123
Aggregation Period: 2023/11/20 10:00 ~ 2023/11/20 10:05
Go to Workspace to View
Go to Workspace for AI Intelligent Analysis
- View: Jumps to the Explorer to view events related to the current SLO (filter condition:
df_monitor_checker_id)
Detection Dimension¶
Detection Dimension: service:kodo,host:test
Related Events: 123
Aggregation Period: 2023/11/20 10:00 ~ 2023/11/20 10:05
Related Detection Rules:
Service {service} latency exceeds threshold, please check as soon as possible >>View
Machine {host} CPU usage exceeds threshold, please check as soon as possible >>View
Related Events:
serviceA latency exceeds threshold, please check as soon as possible 4 times
serviceB latency exceeds threshold, please check as soon as possible 3 times
hostA CPU usage exceeds threshold, please check as soon as possible 5 times
hostB CPU usage exceeds threshold, please check as soon as possible 6 times
Tags¶
Tags: service:kodo,host:test
Related Events: 123
Aggregation Period: 2023/11/20 10:00 ~ 2023/11/20 10:05
Related Detection Rules:
- {{Event Title}} >>View
- View: Jumps to the Explorer to view events related to the current detection rule (filter condition:
df_monitor_checker_id)
Diagram:
Intelligent Aggregation¶
Title Pattern¶
Title: {{Host}} CPU exceeds {Result}%
Related Events: 123
Aggregation Period: 2023/11/20 10:00 ~ 2023/11/20 10:05
Related Detection Rules:
Service {service} latency exceeds threshold, please check as soon as possible >>View
Machine {host} CPU usage exceeds threshold, please check as soon as possible >>View
Related Events:
serviceA latency exceeds threshold, please check as soon as possible 4 times
serviceB latency exceeds threshold, please check as soon as possible 3 times
hostA CPU usage exceeds threshold, please check as soon as possible 5 times
hostB CPU usage exceeds threshold, please check as soon as possible 6 times
- View: Jumps to the Explorer to view all events generated by the current detection rule during the aggregation period (filter condition:
df_monitor_checker_id)
Content Pattern¶
Title: {{Host}} CPU exceeds {Result}%
Related Events: 123
Aggregation Period: 2023/11/20 10:00 ~ 2023/11/20 10:05
Related Detection Rules:
Service {service} latency exceeds threshold, please check as soon as possible >>View
Machine {host} CPU usage exceeds threshold, please check as soon as possible >>View
Related Events:
serviceA latency exceeds threshold, please check as soon as possible 4 times
serviceB latency exceeds threshold, please check as soon as possible 3 times
hostA CPU usage exceeds threshold, please check as soon as possible 5 times
hostB CPU usage exceeds threshold, please check as soon as possible 6 times
- View: Jumps to the Explorer to view all events generated by the current detection rule during the aggregation period (filter condition:
df_monitor_checker_id)
AI Aggregation¶
Title: title: Describes the summary information of this alert.
Handling Suggestion: suggestion: Suggestions for handling the current alert.
{xxx-related} Alert Aggregation: "summary": "Multiple hosts experienced CPU and memory anomalies, with the highest anomaly value being 98% (host 172.16.200.108). Host 1
Related Detection Rules: df_monitor_checker_ids: Involved monitors (Rule IDs).
{xxx-related} Alert Aggregation: "summary": "Multiple hosts experienced CPU and memory anomalies, with the highest anomaly value being 98% (host 172.16.200.108). Host 1
Related Detection Rules: df_monitor_checker_ids: Involved monitors (Rule IDs).
Example:
Title: During the aggregation period, 3 monitors triggered alert events, generating 19 alert notifications.
Handling Suggestion: Prioritize handling hosts with frequent alerts. Host 172.16.200.101 is involved in CPU anomalies, memory anomalies, and communication issues, requiring a comprehensive check. Check alert correlation; multiple monitors (Rule IDs) involve host resources (CPU, memory) and module communication, possibly indicating a systemic issue. Optimize monitoring strategies to reduce alerts triggered repeatedly in a short time, and implement alert noise reduction using time windows.
Host-related Alert Aggregation: Multiple hosts experienced CPU and memory anomalies, with the highest anomaly value being 98% (host 172.16.200.108). Host 172.16.200.101 triggered both CPU and memory alerts simultaneously and requires focused inspection.
Related Detection Rules: title View("rul_e68e2d5e620b40c691128a399de3f479")
Application-related Alert Aggregation: Multiple hosts experienced CPU and memory anomalies, with the highest anomaly value being 98% (host 172.16.200.108). Host 172.16.200.101 triggered both CPU and memory alerts simultaneously and requires focused inspection.
Related Detection Rules: title View("rul_e68e2d5e620b40c691128a399de3f479")
Diagram:
