Notification Channels
Under Alert Management → Notification Channels, configure who receives alerts. Five types are supported: Feishu / DingTalk / WeCom group bots, Email, and custom Webhook.
note
You must create a notification channel first before you can bind it in an alert rule to receive messages.
Group Bots (Feishu / DingTalk / WeCom)
- Add a "group bot" in the group and obtain its Webhook URL:
- Feishu: Group Settings → Group Bots → Add Bot → Custom Bot
- DingTalk: Group Settings → Bots → Add Bot → Custom (if you choose "Custom Keyword" for the security setting, the keyword must include a fixed word from the alert message, such as
Alert) - WeCom: right-click the group → Add Group Bot
- On the "Notification Channels" page, click "Add Channel" → choose a type → enter a channel name and the Webhook URL.
- Bind it in an alert rule. Messages are automatically rendered in each IM's card format (red for alert / green for recovery), with no template to configure.
- Optionally @everyone or @specific members (enter member IDs) to notify the relevant people in the group when triggered.
Email
SMTP details are entered directly in the channel dialog (no longer via environment variables as of 1.4.0):
| Setting | Description |
|---|---|
| SMTP server / port | e.g. smtp.example.com / 465 |
| Username / password | The SMTP account and authorization code; leave blank when editing to keep unchanged |
| Recipients | Comma-separate multiple addresses |
Custom Webhook
Enter any HTTP receiver URL; when triggered, the platform POSTs a standard JSON payload, which you can integrate with your own alert gateway / ticketing system:
{
"title": "alert title",
"event_type": "event type",
"timestamp": "2026-06-10T10:00:00+08:00",
"content": { "structured fields such as rule, instance, current value, threshold": "..." }
}
Verify
Create a temporary rule that is guaranteed to fire (e.g. CPU > 0, with the shortest duration), bind the channel, then click "Check Now"; confirm the notification arrives before deleting the temporary rule.