Website monitor
Use website monitors to poll a public page for availability, exact HTTP status, and response time.
What Cronity checks
Cronity sends a GET request to the configured URL on an interval. A check passes only when the final response exactly matches the expected HTTP status. The event records the status code, request duration, and redirect chain when applicable.
Settings
| Setting | Behavior |
|---|---|
| Check interval | 15 minutes, 30 minutes, 1 hour, 6 hours, or 1 day |
| Request timeout | 1–5 seconds; defaults to 3 seconds |
| Expected HTTP status | An exact status from 100–599; defaults to 200 |
| Failure threshold | Consecutive failed checks required before the monitor becomes Fail; defaults to 2 |
Failure and recovery
- A successful check resets the consecutive-failure count and sets the monitor to OK.
- A failed check below the threshold sets the monitor to Late.
- Reaching the threshold sets it to Fail and opens one incident.
- The next passing check resolves the incident. The monitor page also offers “Run check now.”
When immediate alerts are enabled, assigned integrations are notified when an incident opens; repeated failures in the same incident do not continuously open new incidents.
Redirects and URL safety
Cronity follows at most five redirects and validates every hop. Only public HTTP and HTTPS destinations are allowed; private, loopback, link-local, and otherwise unsafe network targets are rejected. Response content is discarded and reading is capped for safety.