Managing monitors

Day-to-day actions on a monitor, from its detail page or the monitors list.

Pause and resume

Pause a monitor to stop checking it and stop its alerts — useful during planned maintenance. It stays in your list and keeps its history; resume picks checking back up. A paused monitor still counts toward your plan’s monitor limit, but its paused time isn’t checked or alerted on.

Delete

Delete removes the monitor and stops its checks. This can’t be undone — its history goes with it.

Run a check on demand

Diagnose runs a single check right now, outside the normal schedule, and shows you the result — handy for confirming a fix without waiting for the next scheduled check. Diagnose is available for Website / HTTP monitors that have an agent attached.

Heartbeat URL

For a heartbeat monitor, you can rotate its ping URL. This issues a new URL and token and immediately retires the old one — do it if the old URL may have leaked. Update your job to call the new URL.

Dependencies

On any checkpoint or platform monitor, you can pin up to 50 of your own Vendor monitors as dependencies — for example, mark your API monitor as depending on your “AWS” and “Stripe-equivalent” vendor monitors. This is context only: dependencies are shown on the monitor’s detail page so you can see at a glance whether a vendor is involved, but they never change the monitor’s own status. (Vendor monitors themselves can’t pin dependencies.)

Uptime goal (SLA target)

Give a monitor an uptime goal (for example 99.9%). This doesn’t change alerting — it’s the target that Reports measure actual uptime against, so a report can show whether each monitor met or missed its goal.