Adding monitors
Add websites, URLs and TCP ports one by one or thousands at once, and set check options.
Check types
- HTTP(S)
- Requests the URL and expects a status code below 400 (redirects are followed, up to 5).
Without a scheme,
https://is used. Only the response headers are downloaded unless you set a keyword. - TCP port
- Opens a connection to
host:port, e.g.db.example.com:5432ormail.example.com:25. Up when the connection is accepted.
Adding many at once
Paste one target per line (commas work too). Thousands of lines are fine. Lines starting with # are skipped,
invalid lines are reported, and targets you already monitor are not added twice.
Each new domain also gets its own domain status page.
Check options
Open Check options when adding (applied to every pasted target) or a monitor's Settings:
- Alert after
- How many failed checks in a row, from every location, before the monitor is down. Default 2.
- Slow-response alert
- Alerts when successful checks average more than the limit over 3 minutes (default 3 seconds; off, 1, 2, 3, 5 or 10 s). You get "is SLOW" and "is fast again" alerts; slow periods do not count as downtime.
- Request method
- GET (default), HEAD or POST. A POST body is sent as form data.
- Expected status codes
- E.g.
200-299,401. Empty means any code below 400. If you expect a 3xx code, redirects are not followed. - Keyword
- Text the page must contain, or must not contain (e.g. "Error establishing a database connection"). The first 1 MB is searched.
- Headers
- One
Name: valueper line, e.g. anAuthorizationheader. - Basic auth
- Username and password for sites behind HTTP authentication.
- Timeout
- 1–30 seconds (default 10).
- Status page group / hidden
- Group monitors on your status page (e.g. "Websites", "API"), or hide one from public pages.
Pausing and deleting
Hover a monitor in the list to pause, resume or delete it (delete asks for a second click). Paused monitors are not checked and send no alerts; their history is kept. Deleting removes the monitor and its history.