← All docs

Alerts

DotDeployer watches CPU, memory and disk on every server over a 24-hour window and can alert you when one crosses a threshold you set — before it takes a site down, not after.

Steps:

  1. Open the server from Servers, go to its Alerts tab.
  2. Set a threshold for CPU, memory or disk — for example, disk above 90%.
  3. When a server crosses a threshold, DotDeployer raises an alert.

Where alerts show up: an open alert appears in the dashboard’s “Needs attention” list, in the notification bell, and by email — the same two channels DotDeployer uses for every finished job (provisioning, deploy, migration, rollback), so alerts and job results land in one place.

Health checks: separate from threshold alerts, DotDeployer also runs a health check against each site before a deploy switches to it, so a deploy that would break the site never goes live in the first place. DotDeployer also checks each server and each site’s HTTP monitor from outside on its own schedule, every few minutes — this costs you nothing beyond the one request each check makes. A successful check never sends a notification; only when a server or site flips from up to down, or back, do you hear about it, once per flip.

Notifications in general: the bell icon at the top of the app is where you read them, unread first, with a “Mark all read” action — the same list an alert or a finished job lands in.

The DotDeployer server Alerts tab with a disk-usage threshold set