Uptime Monitoring
HTTP and TCP health checks, response keywords, SSL expiry alerts, configurable intervals, and incident management with ErrTap uptime monitors.
HTTP checks
ErrTap polls a URL at a configurable interval and expects a 2xx response. On failure it opens an Incident and fires your alert channels.
Create a monitor in the dashboard: Uptime → New monitor, then supply:
- URL — the endpoint to check
- Interval — how often to poll, from 30 seconds to 1 hour
- Method —
GET(default) orHEAD - Expected status — defaults to
200 - Response keyword (optional) — the body must contain this text, e.g.
"status":"ok". Tick Fail if the keyword appears to invert it (useful forMaintenancepages that still return200). The first 1 MB of the body is checked.
TCP checks
Choose TCP port and enter tcp://host:port (for example tcp://db.example.com:5432). ErrTap opens a connection and closes it immediately — the check passes if the port accepts within the timeout. Use it for databases, SMTP, Redis, game servers, or anything that doesn't speak HTTP. Private and internal addresses are refused, as with HTTP checks.
Check limits
Every plan can poll as often as every 30 seconds. Plans differ in how many checks you can create:
| Plan | Uptime checks |
|---|---|
| Hobby | 3 |
| Pro | 50 |
| Team | 100 |
| Enterprise | Unlimited |
A monitor is marked down (and alerts) only after its configured number of consecutive failed probes — set it per monitor under Advanced → Mark down after (default: 2 in a row, up to 10). One blip on a flaky network doesn't page anyone.
SSL expiry
Every HTTPS monitor also tracks the certificate expiry date. Alerts fire at configurable lead times before expiry (default: 30 days, then 7 days).
Incidents
When a check fails, ErrTap opens an Incident tied to the monitor. An incident records:
- Start time of the outage
- Each failed check during the outage
- Recovery time (when a check returns
2xx) - Total duration
Incidents drive alerting — they fire on open, and optionally on recovery.
Alert configuration
Wire uptime failures to your notification channels under Alerts → Alert rules. Uptime rules fire on:
DOWNTIME— a check has failedRECOVERY— the check is healthy again after an incidentSSL_EXPIRY— certificate expiry is approaching