Monitoring
A monitor checks a Uniform Resource Locator (URL) on a schedule and publishes a status update when the result changes. You do not have to post anything by hand.
How it fits together
- Endpoint: a domain you own and have verified. See endpoints.
- Monitor: a check against that endpoint: type, path, interval, timeout, thresholds and visibility. See monitor types.
- Result: every check is stored. A status update is published only when a threshold is reached, and once more when the target recovers.
A monitor can cover the whole service or one component. A component monitor changes that component's status.
Public and private monitors
| Public | Private | |
|---|---|---|
| Shown on the status page | Yes, as "Automated monitoring" updates | No |
| Emails subscribers | Yes | No |
| Emails the team | Yes | Yes |
| Shortest interval | 5 minutes | Twice the timeout |
Consecutive identical results of a public monitor are grouped on the page, for example "Degraded since 10:02, 4 checks".
Behavior of every check
- The request is a Hypertext Transfer Protocol (HTTP) GET. Headers, authentication, cookies and request bodies cannot be set.
- Redirects are not followed. A 301 counts as a 3xx reply.
- A request that takes longer than the timeout is recorded as a timeout.
- Requests to private and internal network addresses are blocked.
- After a restart, every monitor runs once immediately.
Who can manage monitors
OPERATIONS and ADMIN members can add, edit, test and delete monitors. Every member can view them.