alert-mute-copilot

Creates, edits, and troubleshoots Nightingale alert mute rules via built-in tools.

13.3k|1.8k|Updated Mar 3, 2020
One-click install
npx skills add https://github.com/ccfos/nightingale --skill alert-mute-copilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alert-mute-copilot
Source: https://github.com/ccfos/nightingale/tree/main/aiagent/skill/embedded/builtin/alert-mute-copilot
Command: npx skills add https://github.com/ccfos/nightingale --skill alert-mute-copilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about alert-mute-copilot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I mute an alert in Nightingale?

Create an alert mute rule scoped to a business group with tag conditions matching the target events, a severity list, and a time window. Pass a duration like "2h" for fixed mutes or configure periodic_mutes for recurring windows; the rule takes effect within about 9 seconds.

How do I set up a recurring mute window in Nightingale?

Set mute_time_type to 1 and define periodic_mutes entries with enable_days_of_week (0=Sunday to 6=Saturday, or aliases like weekday) and enable_stime/enable_etime in HH:mm. Cross-midnight ranges such as 22:00 to 06:00 are supported natively.

Why is my Nightingale mute rule not working?

The engine checks gates in order: business group match, disabled flag, datasource list, time window, severity, then AND'd tag conditions. The most common causes are the event belonging to a different business group or a tag value mismatch, such as comma-separated instead of space-separated in values.

Does muting an alert delete existing active alerts in Nightingale?

No. Muting only drops newly evaluated events before persistence and notification; active alerts produced before the mute remain visible. Muted events are also not falsely marked as recovered during the mute period.

What happens when a Nightingale mute rule expires?

Expired fixed-period mutes stop matching but remain in the database and can be queried with expired=1. They are not deleted automatically; admins can bulk-clean them via DELETE /api/n9e/alert-mutes, while periodic mutes are never cleaned up.