A monitor actively checks a target on a configured schedule and records the result. When a check fails (or recovers), Watchplane creates an incident and sends notifications.
Monitor types
| Type | Use case |
|---|---|
| HTTP/HTTPS | Check web endpoints — status codes, response body, headers |
| TCP | Verify a port is open on any host |
| DNS | Validate DNS record resolution |
| SSL | Check TLS certificate expiry and validity |
Check intervals
The minimum check interval depends on your plan:
| Plan | Minimum interval |
|---|---|
| Free | 3 minutes |
| Starter | 1 minute |
| Pro | 30 seconds |
| Business | 30 seconds |
Monitor lifecycle
Created → Checking → Up
↓
Failure detected → Incident created → Notified
↓
Resolved → Incident closed → Recovery notificationA monitor transitions from Up to Down after a configurable number of consecutive failures (default: 1). This reduces false positives from transient network errors.
Notifications
Each monitor can be linked to multiple notification channels. When status changes:
- Down — alert sent immediately (or after the configured failure threshold)
- Up (recovery) — recovery notification sent when the monitor returns to healthy
Notification channels include email, Slack, webhooks, push notifications, and SMS.
Regions
Watchplane runs checks from multiple geographic regions. You can configure which regions a monitor uses — useful for detecting region-specific outages.
Maintenance windows
Schedule periods where a monitor won’t trigger alerts. See Maintenance Windows.
Real-time updates
Monitor status streams via Server-Sent Events (SSE) at /api/v1/projects/{projectId}/monitors/events. The dashboard uses this to update status without polling.