Reduce notification noise in Kibana Universal Alerting

Kibana Universal Alerting has several mechanisms that can silence notifications for an alert. When an alert is silenced, the dispatcher stops processing it before it evaluates any action policy against it. For where this fits in the full dispatch cycle, refer to About action policies.

The following mechanisms let you silence notifications, each at a different scope:

Mechanism Scope When to use
Acknowledge Per alert You're actively investigating a breach and want to silence notifications for it without closing the alert. Clear the acknowledgment when you're done to restore notifications.
Snooze Per series (group) You want to quiet an entire alert series for a defined period, for example, during a known noisy window for a specific host. Snooze expires automatically at the end of the duration.
Resolve Per alert You've fixed the underlying problem and want to close the alert without waiting for the rule to detect recovery. Resolving closes the alert and stops its notifications. If the rule's condition still matches on its next run, a new alert starts for the series, and action policies can send notifications for it.
Maintenance window All action policies in a space You want to pause all action policy dispatching in a space for a planned maintenance period. All active action policies stop dispatching; rule evaluation and alert recording continue. Maintenance windows are configured separately from action policies.

Snooze applies at the group level (by group_hash), not for each individual alert. When you snooze one alert, every alert sharing the same group (all rows with the same rule_id and group_hash) is silenced for the duration. Snoozing one row in the alerts table silences the entire series for that rule.

Note

Snoozing an alert differs from snoozing an action policy. When you snooze an action policy, the dispatch mechanism is paused and every series the action policy processes is silenced. When you snooze an alert, you target one specific series before action policy matching runs, silencing it regardless of which action policy handles it. Use action policy snooze when you want to pause all workflow invocations from a given action policy, for example, during planned maintenance on a destination system.