how-to · watch Open this in the console

Also run a script when the alert gets worse.

Alerts › scripts. The same problem at the same severity is counted. It does not start the script a second time. A higher severity does.

An escalation is announced at once. It does not wait out the delay a fresh alert waits.

Opened starts ticked

Open Alerts › scripts and press new trigger. Name it and choose Who is signed in. Under events, opened is ticked. Escalated and resolved are clear. A disk that stays a warning, even if the percent ticks up, would start this once and not again.

New alert script trigger with only the opened event ticked — Opened is ticked. Escalated is clear. Nothing is saved yet.

Tick escalated as well

Tick escalated. Opened stays ticked. A warning that becomes critical starts the script again. A disk is a warning until 97%, then critical. Accounts server is at 92%, so that disk has not escalated. The same warning repeating does not. An escalation does not wait out the announcement delay. The floor still applies: crit and above skips the warning open and still matches the jump to critical. 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 opened and escalated ticked — Opened and escalated are both ticked. Save has not been pressed.

Only the escalation, with opened cleared, is Run a script only when the alert gets worse. Critical only, so the warning open is skipped and the escalation still matches, is Only run a script for a critical alert. When it clears is Also run a script when the alert clears. The wait is per event — Wait before an alert script runs again.