What problem does it solve?
Configuring alert mute (silence) rules in Nightingale involves business-group scoping, tag matching operators, severity filters, and two distinct time modes, and misconfigured rules silently fail to mute anything. This Skill guides the in-app AI assistant through creating, editing, extending, and diagnosing mute rules correctly.
Core Features & Use Cases
- Mute rule creation: Builds alert_mute configs with tag conditions, severities, and fixed or periodic time windows, then persists them via the create_alert_mute tool.
- Edit and extend: Applies incremental patches through update_alert_mute, including duration extension, temporary disable/enable, and wholesale tag array replacement.
- Troubleshooting: Walks the engine's gate-by-gate matching order (business group, disabled flag, datasource, time, severity, tags) to explain why a mute is not working.
- Use Case: During a two-hour maintenance window on host web01, ask the assistant to mute that machine's alerts; it resolves the business group, builds the tag condition, and creates the rule with a clickable link to verify it.
Quick Start
Ask the assistant to mute alerts for a specific host or rule for a given duration, for example: mute all alerts from web01 for the next 2 hours.