how-to · watch Open this in the console

Run a script only when a machine goes offline.

Alerts › scripts. Downtime is the kind for a machine that has stopped reporting. The kind row is the same list as an alert rule. None of them ticked would match every kind, and the hub refuses a trigger that matches every alert.

A desktop that should stay quiet overnight is a different switch. This trigger still matches it until that machine is left out of offline alerts.
01

Downtime starts ticked, and disk can be ticked too

Open Alerts › scripts and press new trigger. Name it and choose Who is signed in. Downtime is already ticked. Tick disk as well and this draft would also start when a disk fills. Checks, reboots, network path, Docker apps and custom metric stay clear. The floor stays at warn and above.

New alert script trigger with downtime and disk both ticked
New trigger. Downtime and disk are both ticked. Nothing is saved yet.
02

Clear disk and leave downtime

Clear disk. Downtime stays ticked, and it is the only kind. A machine that stops reporting is the only alert that starts this script. Accounts server's disk at 92% is a disk alert, so it would not. The key box stays empty, so every downtime alert matches, on every machine. 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 downtime kind ticked
Downtime is ticked. Disk is clear. Save has not been pressed.

Telling a person about downtime, with no script, is Only tell them about downtime. A desktop that shuts down overnight is Leave a desktop out of offline alerts. A full disk is Run a script only when a disk fills. A failed check is Run a script only when a check fails.