Uptime monitoring, in the same box.

[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.

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] the status pages

One status page per product.

Make a page for each product and pick its apps. Each page answers at its own domain, like status.shop.com, from the one LogNorth server. Anyone can open it. No account, no second tool, no second bill.

• Uptime since the first ping, to 3 decimals: 99.991% since mar 4. Not just the last 90 days.
• The last 90 days as bars, one per day. Green when it was up, red where it was down.
• Every outage of the last 30 days: when it started, and how long it lasted.
• Your notes under each outage. Sign in and say what happened.
• The app's name, never the URL LogNorth pings. On a status domain, the dashboard never answers.

LogNorth counts each day of pings before it deletes them, and keeps the counts. So the uptime goes back to the first ping, while the pings go back 30 days.

[05] 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.