Monitoring & Alerts: jump to another article
Muting alerts
A known issue — a holiday shutdown, a machine already scheduled for maintenance — doesn’t need to page someone every shift while it’s being handled. Muting quiets alerts for a set window without turning monitoring off permanently or losing history.
Three levels
You can mute a site, a line, or a single machine. Muting a site mutes every line and machine inside it; muting a line mutes every machine on it. A machine muted this way shows “Muted via [parent]” and can only be unmuted at the level it was actually muted from — not worked around locally.
Duration and reason
Up to 30 days at a time, with an optional reason (up to 200 characters) shown alongside the mute so anyone who checks later knows why. On mobile, pick from preset durations (1 day, 3 days, 1 week, 2 weeks, 30 days); on the web console, pick a specific resume date. If a shutdown runs longer than 30 days, re-mute once it lapses — there’s no indefinite mute by design.
What muting doesn't do
Checks still record normally, and a muted machine can still go out of spec in its history — muting only suppresses the push notification, the email escalation, and the Alerts inbox entry. Nothing about the underlying reading changes, and unmuting (the Unmute now link, available any time before the resume date) brings alerting back immediately.