Create monitors and alerts

Start by choosing the outcome:

• Service monitors cover HTTP endpoints, CORS, DNS, and heartbeats.
• User-impact monitors cover application-produced journey and metric health.
• Device monitors cover one-device or fleet connectivity.
• Log alert rules call a webhook for matching log events.

Process, disk, TCP socket, and arbitrary script checks are not current monitor types.

Device and fleet monitors create alerts. Service, heartbeat, and user-impact signals can feed incident automation and on-call. Test both failure and recovery in staging, then follow the incident response playbook.