Uptime Monitoring¶
Alongside the check tools, Vernax also monitors availability: heartbeats for jobs and active HTTP checks for endpoints — with alerting by email and webhook on outage and recovery.
Heartbeats (dead man's switch)¶
For cron jobs, backups and anything that should run regularly: your job calls a personal ping URL after each successful run. If the ping is missing for longer than period + grace, the monitor counts as down and you're alerted.
# At the end of the job (report success):
curl -fsS https://<your-vernax-domain>/api/v1/ping/<token>
# Optional before the run — measures the runtime:
curl -fsS https://<your-vernax-domain>/api/v1/ping/<token>/start
# On errors, report explicitly (alerts immediately):
curl -fsS https://<your-vernax-domain>/api/v1/ping/<token>/fail
The request body (up to 256 characters) is stored in the event log — e.g. for short status messages.
Active HTTP checks¶
Vernax calls a URL at your interval and checks:
- Reachability and HTTP status (default: no 4xx/5xx, optionally an exact expected status)
- optionally a keyword that must appear in the response
- the latency is recorded
Status & alerting¶
| Status | Meaning |
|---|---|
| 🟢 up | Last ping/check successful |
| 🟡 late | Ping overdue, grace period still running |
| 🔴 down | Grace exceeded or check failed |
| ⚪ new / paused | No ping yet or paused |
On down and on recovery an email goes to the workspace owner; optionally
Vernax also calls a webhook URL with a JSON payload.
Limits¶
Monitors per workspace: Free 2 · Starter 10 · Pro 50 · Team unlimited. Minimum interval for active HTTP checks: Free/Starter 15 min · Pro 5 min · Team 1 min.