What problem does it solve?
Configuring Nightingale (n9e) notify rules requires translating natural-language routing requirements (tiered severity, time windows, label filters) into a correct NotifyConfig JSON array, which is error-prone and full of pitfalls like cross-midnight windows and wrong operator syntax.
Core Features & Use Cases
- Notify Rule Lifecycle Management: Create, edit, copy, and troubleshoot notify rules via built-in tools, with proposal-based updates that show users a change list before committing.
- Routing Decomposition: Maps composite requirements (e.g., "P1 phone call during work hours, DingTalk only after hours") into multiple NotifyConfigs using six proven templates covering tiered routing, time windows, recovery filtering, business-group routing, label canary, and catch-all rules.
- Pitfall Detection & Dry-Run Verification: Proactively corrects known misconfigurations (comma-separated
in values, wrong week numbering, name-bound business groups) and verifies rules with real historical events via the test endpoint.
- Use Case: A user says "route P1 alerts to phone + DingTalk during working hours, phone only outside working hours" — the Skill decomposes this into three NotifyConfigs, looks up real channel and team IDs, asks for any missing bot tokens with doc links, and creates the rule.
Quick Start
Ask the assistant to create a notify rule that sends P1 alerts by phone and P2/P3 alerts by email to your on-call team.