Skip to content

Pausing monitors

Every monitor has an Enabled toggle. Switch it off and the monitor becomes Paused: UpAll stops checking it until you switch it back on. Pausing is reversible, immediate, and keeps everything the monitor has ever recorded.

What stops

  • Checks stop. No probes are sent and no results are recorded while the monitor is paused.
  • Automatic incidents stop with them. Incidents open when consecutive checks fail; with no checks running, a paused monitor can't accumulate failures, so it never opens an incident or emails anyone.

What remains

  • The monitor and its full configuration — target, thresholds, site — untouched, ready to resume.
  • The complete history: raw results (kept 100 days) and the permanent daily rollups. Charts still show everything up to the moment of the pause (reading monitor charts).
  • Visibility: the monitor still appears in lists with the Paused status, so it reads as deliberately off — distinct from Unknown, which means checks should be arriving but aren't (monitor statuses explained).

Paused time is neither uptime nor downtime — there are simply no checks. Monthly reports state measurement coverage, so a long pause shows up honestly as reduced coverage rather than as invented availability (monthly SLA reports).

Re-enabling

Switch Enabled back on and checking resumes on the monitor's normal interval — the first check runs within a minute. Statuses, charts, and incident logic all pick up from live data again.

Planned maintenance: pausing is the tool

UpAll has no maintenance-window feature — there's no way to schedule downtime suppression in advance or mark a period as expected downtime. When you're about to reboot a server, patch a service, or take a link down deliberately, the working practice is:

  1. Pause the affected monitors just before you start.
  2. Do the work.
  3. Re-enable them as the closing step of the change.

Skip step 1 and the monitoring reacts exactly as designed: checks fail, incidents open, and the whole staff is emailed about downtime you caused on purpose (how incidents open and close). Skip step 3 and the system is silently unwatched — a paused monitor protects nobody, which is why re-enabling belongs on the checklist as an explicit step, not an afterthought. The visible Paused status is your safety net: a quick scan of the monitor list at the end of a maintenance evening shows anything left off.

If the work will disrupt several of a client's systems, consider also announcing it: staff can create a manual incident with a bilingual title and body to tell the story properly — see manual incidents.