Notification Channels

Configure alert recipients under "Alert Management → Notification Channels". Five channel types are supported: Feishu, DingTalk, and WeCom group robots, email, and custom Webhook.

note

Create a notification channel before binding it in an alert rule to receive messages.

Group Robots (Feishu/DingTalk/WeCom)

1. Add a group robot in the 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 alert
   • WeCom: Right-click the group → Add group robot
2. On the "Notification Channels" page, click "Add Channel", select the type, and enter the channel name and Webhook URL.
3. Bind the channel in alert rules. Messages are automatically rendered in each IM card format (red for alert, green for recovery), with no template configuration required.
4. Optionally mention all members or specified members (member IDs). Related people will be reminded in the group when the alert fires.

Email

Enter SMTP information directly in the channel dialog (environment variables are no longer used since 1.4.0):

Configuration	Description
SMTP server/port	For example, smtp.example.com/465
Username/password	SMTP account and authorization code. Leave blank during editing to keep the existing value
Recipients	Separate multiple recipients with commas

Custom Webhook

Enter any HTTP receiver URL. When triggered, the Ops Platform posts a standard JSON payload that can integrate with a custom alert gateway or 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, and threshold": "..." }
}

Verification

Create a temporary rule that is guaranteed to fire, such as CPU > 0 with the shortest duration. Bind the channel, click "Check Now", confirm the notification is received, and then delete the temporary rule.