HTTP monitors
Uptime checks with status codes, keywords, intervals and thresholds.
An HTTP monitor is the reverse of a heartbeat: Vivere makes the request. Use it for websites, APIs, health endpoints and anything that should answer.
| Setting | Meaning |
|---|---|
| URL | Must be public. Requests to private, loopback or link-local addresses are refused. |
| Method | GET, HEAD or POST (empty body). |
| Interval | How often to check. 1 minute on paid plans, 5 minutes on Free. |
| Timeout | 1–60 seconds. A response slower than this is a failure. |
| Expected status | An exact status code, or 0 to accept any 2xx or 3xx. |
| Keyword | Optional text that must appear in the first 512 KB of the body. |
| Failures before alert | Consecutive failed checks needed to go Down. 2 avoids alerting on a single blip. |
Requests carry the user agent Vivere-Monitor/1.0 (+https://vivere.dev) and follow up to five redirects. A monitor is Up after one successful check, Down after the threshold, and alerts on both transitions.