Alerts.

Work an open alert

Ack, discuss, resolve, or accept a condition that is known and fine.

See resolved alerts on the alerts page

Open + acked hides anything that already cleared. Resolved brings those rows back.

Acknowledge an alert

Ack means a person saw it. The alert stays open. A comment is optional.

Resolve an alert by hand

Resolve closes an alert when the hub has not noticed the condition cleared. A comment is optional.

Leave a comment on an alert

Ack, resolve and release ask for a comment. The row keeps the thread for the next person.

Accept a known condition

Disk always 92%? Say so. Alerts stay recorded; nobody is paged; BE AI stops proposing.

Accept a condition until a date

Until is a way back. On that date the alert re-opens, even if the disk never got worse.

Accept a disk until free space falls

A free-GB floor is a way back. The alert re-opens when free space drops under that number.

Release an accepted condition

Release puts a known condition back in the queue. Investigations and notifications resume.

Tell someone when a machine needs attention

Add a notification rule — who gets email, SMS, a call or a webhook when an alert opens.

Tell them when an alert clears

A rule can send a second message when the condition clears. That is on until you clear the box.

Turn an alert rule off

Off takes the rule out of the list. Alerts still open. Nobody is told by that rule until you turn it on.

Delete an alert rule

Delete removes the rule. The first press asks you to confirm. Alerts already open stay open.

Change an alert rule

Edit opens the same rule. Save changes keeps the row. Test sends one synthetic message and does not open an alert.

Send a test of an alert rule

Test sends one synthetic message to the rule's contacts. It does not open an alert on a machine.

Limit an alert rule to servers

Tick a machine type and the rule covers only those machines. Empty still means every type.

Limit an alert rule to workstations

Tick a machine type and the rule covers only those machines. Empty still means every type.

Limit an alert rule to laptops

Tick laptop. The rule covers only those machines. Empty still means every type.

Limit an alert rule to network devices

Tick network device. The rule covers only those machines. Empty still means every type.

Limit an alert rule to hypervisors

Tick hypervisor. The rule covers the host. A guest is a machine of its own type.

Limit an alert rule to printers

Tick printer. The rule covers only machines whose type is printer. Empty still means every type.

Limit an alert rule to type other

Tick other. The rule covers only machines whose type is other. Empty still means every type.

Limit an alert rule to one site

Tick a tag. The rule covers that tag and everything nested under it. A machine with no tag is left out.

Limit an alert rule to one role

Tick a role tag. The rule covers that path and everything nested under it. A machine with no tag is left out.

Limit an alert rule to servers in one role

A type and a tag combine. The machine has to be both. Two types, with no tag, means either type.

Only tell them about disk alerts

Tick disk on a rule and the other kinds stay quiet. Empty still means every kind.

Only tell them about downtime

Tick downtime on a rule and disk, checks, and the other kinds stay quiet.

Only tell them when the network path changes

Tick network path on a rule. A new external IP or a WAN failover is the message. The other kinds stay quiet.

Only tell them about a Docker app

Tick Docker app on a rule. An unhealthy or restarting app is the message. The other kinds stay quiet.

Only tell them about a failing check

Tick checks on a rule. A check that fails is the message. The other kinds stay quiet.

Only tell them about a reboot

Tick reboots on a rule. A machine that restarted is the message. The other kinds stay quiet.

Also tell them about a notice

The floor starts at warning and above. Info and above includes a notice, such as a routine reboot.

Only tell them about a custom metric

Tick custom metric on a rule. A post that goes down, or a missed post, is the message. The other kinds stay quiet.

Send an alert to Slack or Teams

A webhook contact posts the alert as JSON to Slack, Teams, Discord, PagerDuty, or your own URL.

Send an alert as your own JSON

Custom format is a webhook contact whose body you write. Placeholders fill in the alert, the machine and the link.

Text or call when an alert opens

The same rule as email, with the channel set to SMS or a phone call.

See what an alert sent

Alerts › sent is every delivery: email, SMS, a call, or a webhook. Empty means nobody has been told yet.

Run a script when an alert opens

A trigger starts a saved script when an alert is announced — on that machine, or on a different one.

Run a script on the machine that raised the alert

Run on can be the machine that alerted, instead of a list you tick. Whoever matches is the target.

Run a script on every machine in a role

Run on can be a tag. Every machine with that path, or nested under it, is a target.

Run a script only when one machine alerts

When starts as any matching machine. Pick one name and only that machine's alerts can start the script.

Run a script only when a disk fills

Kinds start on downtime. Tick disk and clear downtime, and a full disk is the only alert that starts the script.

Run a script only when a check fails

Kinds start on downtime. Tick checks and clear downtime, and a failed check is the only alert that starts the script.

Run a script only when a machine restarts

Kinds start on downtime. Tick reboots and clear downtime, and a restart is the only alert that starts the script.

Run a script only when the network path changes

Kinds start on downtime. Tick network path and clear downtime, and a new external address or a WAN failover is the only alert that starts the script.

Run a script only when a Docker app is unhealthy

Kinds start on downtime. Tick Docker apps and clear downtime, and an unhealthy or restarting app is the only alert that starts the script.

Run a script only when a custom metric goes down

Kinds start on downtime. Tick custom metric and clear downtime, and a post that goes down, or a missed post, is the only alert that starts the script.

Run a script only when a machine goes offline

Downtime starts ticked. Clear every other kind, and a machine that stops reporting is the only alert that starts the script.

Run a script for one disk only

A key is one alert. disk:/ is the root volume. An empty key still means every disk of the kinds you ticked.

Wait before an alert script runs again

Cooldown starts at 900 seconds. The same alert on the same machine cannot start the script again until that wait is over.

Fill a script answer from the alert

A question on the script is answered on the trigger. Type it once, or copy a fact from the alert. The shape is checked before anything runs.

Only run a script for a critical alert

The floor starts at warn and above. Crit and above skips a warning. Info and above includes a notice.

Also run a script when the alert clears

Events start on opened. Tick resolved as well, and the script starts again when the condition clears.

Run a script only when the alert clears

Opened starts ticked. Clear it and tick resolved, and the script starts when the condition clears, not when it opens.

Also run a script when the alert gets worse

Events start on opened. Tick escalated as well, and a warning that becomes critical starts the script again.

Run a script only when the alert gets worse

Opened starts ticked. Clear it and tick escalated, and a warning that becomes critical is the only event that starts the script.

Turn an alert script off

Enabled starts ticked. Clear it and save, and the row stays, marked off. It does not run.

Change a script that runs when an alert opens

Edit opens the same trigger. Save keeps the row. The first press does not ask you to confirm.

Remove a script that runs when an alert opens

Delete removes the trigger. The first press asks you to confirm. Alerts already open stay open.