~ $ man 7 uptime
Uptime monitoring, in the same box.
LogNorth pings your app every minute. When it stops answering, you get an alert. When it's back, you get another. No second tool to run, no second bill.
up 84ms · last ping 12s ago
last failure 15:21 · 503 · 1,204ms
[01] the ping
A ping every minute.
Give an app its URL when you create it, or later on the Apps page. LogNorth sends a GET every minute, waits up to 5 seconds, and follows one redirect.
| the answer | counts as |
|---|---|
| 2xx, 3xx, 4xx | up: your app answered |
| 5xx | failed |
| no answer within 5s | failed |
| refused, DNS, or TLS error | failed |
A 404 or a 401 still means your app is running, so only a 5xx or no answer counts as a failure.
[02] the alert
Three misses, one alert.
- 3 failed pings in a row mark the app down, and one alert goes out.
- When it answers again, a second alert says it's back and how long it was down.
- Alerts go where your other alerts go: Telegram, a webhook, ntfy.sh, or email.
- An outage that starts in quiet hours alerts when they end.
- No alerts in the first 10 minutes after LogNorth starts, so a restart doesn't page you.
[03] the history
30 days of pings. Every one.
LogNorth keeps each ping with its time, HTTP status, and response time. The Endpoints page draws the last 24 hours in 96 bars. Hover a red one to see what failed: HTTP 503 ×2, or no answer within 5s.
Home and the Apps page show each app's ping and its 24-hour uptime. The status bar shows the app you're in: up 84ms, or down 12m in red.
[04] why here
Down, and why, on one screen.
An uptime tool tells you the site is down. LogNorth also has the logs of the requests that failed, so the next click shows why.
The pings come from your LogNorth server with the user agent LogNorth Uptime/1.0 (+https://lognorth.com), so you can let them through a firewall.
One thing it can't do: if the box LogNorth runs on goes down, nothing pings. Run LogNorth on a different box than the app it watches.
Logs, errors, alerts, and uptime. One box. $99 once.