Warning Analysis
In the "Warning Analysis" module you can configure warning rules, warning metrics, and push channels to monitor production performance fluctuations. You can create a warning rule from scratch, set detailed warning info, metrics, and push modes. You can also use alert template management to create warnings quickly from business templates. In the alert list you can toggle the rule's effective state. The warning history module lets you review the project's recent warning trend, composition, and detailed records.
1. Create a Warning Rule
Click "Create New Alert Rule" to enter the creation page.
1) Step 1: Configure Warning
Form fields:
- Basic information
| Field | Description |
|---|---|
| Metric type | Defaults to basic performance metrics. |
| Alert type | Shows hourly-flow data under the chosen filters. |
| Alert platform | Defaults to the current platform; alert rules are not shared across platforms. |
| Alert name | A custom name. |
| Expiration time | When the rule expires; set manually. |
| Minimum match count | Optional. If the match count is below this value, the alert is suppressed. |
| Task interval | How often the alert detection task runs. |
| Metric statistical window | The time range used to compute the metric, e.g. "last 1 day" means each detection uses the last day's data. |
- Filter conditions
Set the version, scene, device, and quality settings used by the detection. Version and scene are mandatory; device and quality default to "all".
- Alert rules
| Field | Description |
|---|---|
| Match logic | Match all rules or any rule; defaults to "match all". |
| Alert metric | Pick metrics with day-over-day, period-over-period, or absolute thresholds. The threshold can be a value or a percentage. The "AI Threshold Recommendation" feature can compute a threshold for you. |
| Alert grouping | Off by default. Once enabled, the data is grouped by the chosen dimensions and any group satisfying the conditions triggers an alert. |
- Warning preview
Click "Preview" to view the real metric trend and triggered alerts over a recent period. Switch between rules using the upper-left selector.
2) Step 2: Configure Warning Notification
Form fields:
| Field | Description |
|---|---|
| Notification language | Chinese or English; default is Chinese. |
| Push condition | Default is "only push when triggered"; can switch to "push every detection". |
| Effective hours | Default is 24/7; you can specify a window. |
| Email recipients (optional) | Email addresses for receiving alerts; multiple addresses separated by ";". |
| Notification webhook | Supports WeCom / DingTalk / Lark / Slack robot webhook URLs. WeCom also supports @-mentioning users. |
| Briefing type | Text alert or image-report alert. |
- Send test alert
After completing configuration, you can send a test alert to verify the channel works.
2. Alert Template Management
You can save a warning configuration as a template and create new warnings from it later. Templates can be managed in the alert list.
3. Alert List
The list shows the warnings the project has created and their basic information, together with the daily warning-trigger trend per rule. In the actions column you can toggle the rule's effective state, clone, edit, or delete it, and view its operation history.
4. Warning History
The Warning History module shows the project's total warning count today and the trend over the last 24 hours and 30 days.
1) Alarm list
Sorted by time descending, the list shows the alarm rules and their counts that have triggered most recently.
Click an entry's count or rule content to enter the rule's alert detail page.
2) Alarm detail page
View the trend, the matched matches, the metric, and the metric delta for the rule.
Click "View All Alarm Counts" to see every historical alert for that rule.
Click "Performance Analysis" to jump to the Performance Analysis page for deeper investigation.
