Nightingale introduced new notification rules from v8.0.0-beta7, making it easy to integrate with various notification channels.
Starting from v8.0.0-beta7, Nightingale introduced new notification rules that make it easy to integrate with all kinds of notification channels. However, beta7 was not yet mature; this feature became truly production-ready from beta8 onwards.
- Nightingale Major Revamp: Abstracting Notification Rules to Enhance Alert Notification Flexibility
- Nightingale v8.0 New Notification Rules | Integrating with DingTalk Alerts
- Nightingale v8.0 New Notification Rules | Integrating with WeCom Alerts
- Nightingale v8.0 New Notification Rules | Integrating with Feishu Alerts
- Nightingale v8.0 New Notification Rules | Integrating with DingTalk Alerts, How to Configure @ Mentions
- Nightingale v8.0 New Notification Rules in Practice | Integrating with DingTalk, Feishu, and WeCom
FAQ
Q1: What is the relationship between notification rules and alert rules?
A: Alert rules are responsible for detection, and notification rules are responsible for distribution. After an alert event is triggered, v9’s new notification mechanism uses the notification rules to find matching recipients and channels. An alert rule can be associated with multiple notification rules (different levels / business dimensions can go through different channels).
Q2: How do I split notification rules by business group?
A: Notification rules themselves have an “applicable business group” field. Common splits:
pay-prod-critical— business group pay-prod + level S1 → phone + DingTalk;pay-prod-warning— business group pay-prod + level S2 → DingTalk;default-all— fallback rule, covering business groups not separately configured.
Q3: What’s the difference between “recipients” and “recipient teams” in notification rules?
A:
- Recipients: precisely specify certain users — suitable for critical alerts sent to specific responsible persons;
- Recipient teams: sent to all team members — suitable for on-duty scenarios, automatically updated when team members change.
It’s recommended to use teams as the main approach to avoid the recipient list getting out of sync with organizational changes.
Q4: Can a user choose in their own profile “alerts I don’t want to receive”?
A: Currently, user self-service filtering is not supported. All filtering must be defined at the notification rule level (e.g., by business group / level / time period). Personal-level “do not disturb periods” can currently only be achieved by configuring multiple rules.
