Website & API monitoring
Check response codes, latency, text, or a JSON field. Keep custom request headers encrypted.
GET /health→$.status == "ok"Keep an eye on your APIs and websites.
Get the failure context. Know when they recover.
| STEP | WHAT HAPPENS | WHAT YOU SEE |
|---|---|---|
| 01 / Check | HTTP response and assertions are evaluated | Measured status, response time, TLS expiry |
| 02 / Confirm | A second failed check confirms an incident | One incident with failure evidence |
| 03 / Notify | Email and Slack alerts enter a durable queue | Delivery attempts and provider acceptance |
| 04 / Recover | Two successful checks confirm recovery | A resolved incident and recovery notification |
The essential monitoring loop, in one workspace.
Check response codes, latency, text, or a JSON field. Keep custom request headers encrypted.
GET /health→$.status == "ok"Two consecutive failures open an incident. Acknowledge ownership and follow the recovery timeline.
suspect→down→recoveredEmail and Slack delivery logs show acceptance or failure. Temporary failures retry automatically.
queued→attempted→acceptedKeep failed checks, confirmation and recovery together. A missing probe becomes “Unknown”. Pausing a check keeps its open incident visible.
View your incidents →GET /health → 503Same probe recheck → 503Incident + notification queuedFirst healthy checkSecond healthy checkVerify your email. Add an endpoint. Receive real signals.