Skip to content

Silences and mutes

None of these change what happens to an event — it still arrives, still opens or updates an incident, and stays fully visible in the inbox and the incident list. They only decide whether a destination is notified about it, and only for alerting reasons: a correction about an incident a destination was already told about is never held back by any of them, so no channel keeps showing an alert that has actually cleared.

There are three, at three different scopes:

Scope Set from
Silence Every source in the workspace, matched by conditions Notifications › Muting
Mute One source, everything from it Mute a source… on the Muting tab, or that source’s own detail page
Snooze One specific incident The incident itself, in the inbox

A mute is really a silence narrowed to one source with no conditions — it shows up in the same Active now list on the Muting tab, so you always see everything currently held back in one place. Quiet hours, the third way to hold messages back, sit further down the same tab, with their own Enable quiet hours switch. The tab starts with its two actions — + Silence and Mute a source… — and explains all three ways until your first silence exists.

Open Notifications → Muting → + Silence. The silence opens in a panel on the right; saving closes it, with the new silence focused in the list, and closing it with unsaved changes asks first. Give it:

  • Conditions under Hold messages about events where — the first one starts on source, with nothing picked yet. The same fields as a routing rule, narrowed to what a silence can match: source, resource, type, severity, tags and any metadata.<key>, such as metadata.composeProject (action, title, body and time are rule-only). A metadata value is matched as text unless you tick Match as a number (or Match as true or false), as in a rule. The field list shows a few values each field carried in your recent events. Every condition must hold for a message to be held back; at least one is required, or it would silence the entire workspace.
  • For — 1 hour, 4 hours, Until a time on the workspace’s clock, or Custom… to set the start and end yourself.

Once the conditions are complete, one line sums the silence up — what it holds back, for whom and until when: Holds back messages where resource is nas, for every destination, until 18:00. The panel also asks the server what the silence would hold right now and says so: Matches 1 open incident and 12 events from the last 7 days., followed by the titles of the first five open incidents it would hold. The preview runs the same matcher over the same fields as the saved silence, metadata included, so what it counts is what the silence holds.

While it’s active, a held-back notice shows in the incident’s timeline as SKIPPED: silenced.

Active now lists every silence and mute that is holding notices back, with what it matches, until when and how many notices it has held so far (one per notice, however many destinations it would have reached); Scheduled ones follow, and ended ones fold away under Ended. End one early with End now (a mute says Unmute), or open Edit for the same panel — a mute’s has no conditions. The list follows the clock while you watch it: one whose window runs out moves to Ended on its own. If something is unfinished — a condition with a field but no value, say — the message sits under that condition.

Clearing the Name field of a silence and saving removes the name — the list then shows it as Unnamed silence.

From a source’s detail page, Mute it for a set duration or indefinitely — or use Mute a source… on the Muting tab, pick the source, and choose how long. The panel then sums it up: Holds back every message about pve-home, for every destination, until you unmute it. Its events keep arriving and keep opening incidents; only the alerts about them stop. Unmuting it ends the mute immediately — anything it was holding back that’s still open and unacknowledged gets a notice right away, so you’re not left thinking everything’s fine.

From the inbox, snooze one incident until a specific time. It stops alerting until then, and clears any acknowledgement it had. When the time is reached, it returns to open with one notice saying so — snoozing isn’t a way to make something go away, only to defer it. A resolved incident can’t be snoozed.

  • Quiet hours — the workspace’s one nightly window, by destination threshold rather than by matcher
  • Routing rules — the condition fields a silence’s matchers share with a rule’s when