Skip to content

Silence alerts during maintenance

You’ll get: no notifications for a maintenance window you set in advance, without losing visibility — incidents still open and show up in the inbox, they just don’t notify anyone while the silence is active.

  • A workspace on InfraInbox, with the source(s) or resource(s) you’re about to work on already sending events.

Go to Notifications → Muting and click + Silence. The silence opens in a panel on the right, with the Muting tab still in view. Give it a name that says what the maintenance is (e.g. “PVE01 firmware update”).

Under Hold messages about events where, add one or more conditions — the first starts on source — and every one must hold for a message to be held back, so add enough to cover exactly what’s affected: a specific source, a resource, a type, a severity, or a tag. The field list shows a few values each field was seen with in your recent events, so you can pick resource and see nas, pve-1, … beside it. A silence with no conditions isn’t allowed, on purpose: it would hold back the whole workspace.

As soon as the conditions are complete, the panel says what the silence would hold right now: Matches 1 open incident and 12 events from the last 7 days. If it says 0, the conditions probably don’t match what you meant.

If you’d rather silence one entire source with one click instead of building a matcher, use Mute a source… on the Muting tab, or Mute on that source’s own page, instead — same mechanism, pre-filled to that source, and it can be left open-ended until you unmute it.

Under For, pick 1 hour, 4 hours, Until a time on the workspace’s clock, or Custom… to set Starts and Ends yourself (in the workspace’s own time zone, which the panel names). A maintenance window you set in advance is a Custom… one. If maintenance runs long, come back and click End now on this silence under Active now when you’re done, rather than waiting for the original end time.

Click Start silence.

While the silence is active:

  • Anything it matches still opens or updates an incident, and still shows up in the inbox — a silence never hides an incident, only the notification about it.
  • On the incident’s activity timeline, a held-back notice shows as SKIPPED: silenced, so you can confirm afterwards that the silence actually caught what you expected.
  • Trigger a matching test event (or use Preview routing beforehand) to confirm the matchers are right before the real maintenance window starts.
Symptom Likely cause
Notifications still arrive A matcher is more specific than the event (e.g. matching a resource your maintenance doesn’t actually touch), or the window’s time zone isn’t what you expected — it’s always the workspace’s zone, not your browser’s.
Nothing shows in the inbox either That’s not this silence — check whether a routing rule for this event drops it or keeps it in History regardless of any silence.
  • Silences and mutes — the full reference, including mutes.
  • Only critical alerts at night if what you want is a recurring nightly quiet period rather than a one-off window — its own Enable quiet hours switch sits further down the same Muting tab.