Uptime Monitoring
A ping every minute, alerts on down and recovery, 30 days of history
LogNorth pings each app’s URL every minute and alerts when it stops answering.
Set it up
Section titled “Set it up”Paste the URL when you create the app. To add or change it later, open Apps and click [edit] on the app’s uptime line. The same editor turns the check off and on.
The first ping runs within a minute.
What counts as down
Section titled “What counts as down”LogNorth sends a GET with a 5-second timeout and follows one redirect.
| The answer | Counts as |
|---|---|
| 2xx, 3xx, 4xx | Up. The app answered. |
| 5xx | Failed |
| No answer within 5 seconds | Failed |
| Connection refused, DNS, or TLS error | Failed |
3 failed pings in a row mark the app down.
Alerts
Section titled “Alerts”| When | Alert |
|---|---|
| The app goes down | One alert, with the URL |
| It answers again | One alert, with how long it was down |
Alerts go to the channels in Settings > Alerts: Telegram, a webhook, ntfy.sh, or email. An outage that starts in quiet hours alerts when they end. There are no alerts in the first 10 minutes after LogNorth starts, so a restart does not page you.
History
Section titled “History”LogNorth keeps every ping for 30 days: its time, HTTP status, response time, and error.
- Endpoints page: the last 24 hours in 96 bars of 15 minutes, red where a ping failed. Hover a bar to see its pings, the average response time, and what failed, for example
HTTP 503 ×2orno answer within 5s. - Home and Apps: each app’s latest ping and its 24-hour uptime.
- Status bar: the app you’re in:
up 84ms, ordown 12min red.
Firewalls
Section titled “Firewalls”The pings come from your LogNorth server with this user agent:
LogNorth Uptime/1.0 (+https://lognorth.com)What it does not do
Section titled “What it does not do”The ping runs on your LogNorth server. If that box goes down, nothing pings and nothing alerts. Run LogNorth on a different box than the app it watches.