Monitoring
Website Monitoring
HTTP/HTTPS, SSL, DNS, and heartbeat checks against any public or internal endpoint.
Website monitors don't require an agent — they're checks MonSPHERE performs directly against a target URL or host on a schedule you define.
Monitor types
| Type | What it checks |
|---|---|
http / https | Response status, latency, and optional body/header assertions |
ping | ICMP reachability and round-trip latency |
tcp | Raw TCP port connectivity |
dns | DNS resolution correctness and latency |
ssl | Certificate validity and expiry |
heartbeat | Inbound "I'm alive" pings from cron jobs and background workers — alerts when a heartbeat is missed, not when a check fails |
Creating a monitor
curl -X POST https://api.monsphere.com/api/v1/monitors \
-H "X-Api-Key: msk_live_..." \
-H "Content-Type: application/json" \
-d '{
"name": "Marketing Site",
"type": "https",
"target": "https://monsphere.com",
"intervalSeconds": 60
}'Status lifecycle
A monitor has a status (active/paused, whether it's currently being checked) and a currentStatus (pending/up/down, the result of the most recent check). A monitor transitioning to down is what alert rules evaluate against.
SSL expiry monitoring
ssl-type monitors track certificate expiry independently of uptime — you can be alerted 30, 14, or 7 days before a certificate expires, before it ever causes an outage.