All pages
Run
Uptime and status pages
Know when an application stops answering, and let its users see that it is up.
Checks
Every running application is asked for its health check path once a minute, from inside the server — a check is not a visitor and does not wake an application that sleeps. An answer from 200 to 399 within 10 seconds is up.
- Checked every
- 60 seconds
- Down after
- 3 failed checks in a row
- Each check kept
- 14 days
- Daily figures kept
- 90 days
Three failures in a row open an incident and tell you why in a few words — refused, timeout, http 502. The first good answer closes it and says how long it lasted. Set where you hear it under Settings → Notifications, category Application problems.
The project's Overview shows uptime over 24 hours, 7 and 30 days, the average response time, one bar per day for 90 days and the incidents.
arrah uptime my-api
Public status page
Off until you turn it on, per project: Overview → Uptime → Turn on public page, or:
arrah uptime my-api --status-page on
Anyone with the address /status/<project> then sees the project's name, whether it is up, its uptime and its incidents with their length. Not the application's address, not why a check failed, nothing about your account. Turning it off makes the address show nothing.