how-to · watch Open this in the console

Run a script only when a check fails.

Alerts › scripts. Checks is the kind for a custom check. A full disk is a different kind, even when a free-space check is what you meant.

The hub refuses a trigger with no kind ticked. One kind, or several, is the match.

Downtime starts ticked

Open Alerts › scripts and press new trigger. Name it and choose Who is signed in. Downtime is already ticked. Checks is clear, so a failing check would not start this draft. Disk, reboots, network path, Docker apps and custom metric are clear too.

New alert script trigger with downtime ticked and checks clear — New trigger. Downtime is ticked. Checks is clear. Nothing is saved yet.

Tick checks and clear downtime

Tick checks and clear downtime. A custom check that fails is the only kind that starts this script. Accounts server's disk at 92% is a disk alert, so it would not. The nightly backup check on that machine is already resolved, so it would not start one either. The key box stays empty, so every check matches, on every machine. Warning and above is the severity floor. Press save when this is the one you want. This shot stops before that. Cancel drops the draft. Run on is still these machines, and none is ticked, so a save would also need a target.

Alert script trigger with only the checks kind ticked — Checks is ticked. Downtime is clear. Save has not been pressed.

A full disk, not a failed check, is Run a script only when a disk fills. A restart is Run a script only when a machine restarts. A new external address or a WAN failover is Run a script only when the network path changes. A Docker app is Run a script only when a Docker app is unhealthy. A custom metric is Run a script only when a custom metric goes down. Telling a person about checks, with no script, is Only tell them when a check fails. Writing the check itself is Add a disk or ping check.