Notification Channels
Configure alert recipients under "Alert Management → Notification Channels". Feishu, DingTalk, and WeCom group robots, email, and custom Webhooks are supported.
After creating a notification channel, bind it in an alert rule to receive notifications.
Group Robots (Feishu/DingTalk/WeCom)
-
Add a robot to the corresponding group and obtain the Webhook URL:
- Feishu: Group settings → Group bots → Add bot → Custom bot
- DingTalk: Group settings → Bots → Add bot → Custom (if "Custom keyword" is selected in security settings, the keyword must include a fixed word in the alert message, such as
告警) - WeCom: Right-click the group → Add group robot
-
On the "Notification Channels" page, click "Add Channel", select the type, and enter the channel name and Webhook URL. Select @all members or @specified members as needed; enter member IDs when specifying members.
-
Bind the channel in an alert rule. Notifications use each platform's card format; no template configuration is required.
Email
Enter SMTP information in the notification channel configuration dialog. Environment variables are no longer used for configuration since 1.4.0:
| Configuration | Description |
|---|---|
| SMTP server/port | For example, smtp.example.com/465 |
| Username/password | SMTP account and authorization code; leave blank when editing to keep the existing value |
| Recipients | Separate multiple recipients with commas |
Custom Webhook
After an HTTP receiver URL is entered, the Ops Platform sends JSON through POST when an alert fires. Use it to integrate an alert gateway or ticketing system:
{
"title": "告警标题",
"event_type": "事件类型",
"timestamp": "2026-06-10T10:00:00+08:00",
"content": { "规则、实例、当前值、阈值等结构化字段": "..." }
}
Create a temporary rule that can fire, for example by setting the CPU condition to greater than 0 and using the shortest duration. Bind the channel and click "Check Now". After confirming receipt of the notification, delete the temporary rule.