Add uptime monitoring with operator alerts #27

Open
opened 2026-07-01 01:01:39 +00:00 by manlycucumber · 1 comment
manlycucumber commented 2026-07-01 01:01:39 +00:00 (Migrated from github.com)

Problem

When the site or API goes down, operators must be paged rather than finding out from users.

Acceptance criteria

  • An external monitor checks the health endpoint on a short interval
  • Sustained failures trigger an alert through at least one operator channel (email/webhook)
  • Recovery sends an all-clear notification
  • Alert thresholds avoid flapping on single transient failures
## Problem When the site or API goes down, operators must be paged rather than finding out from users. ## Acceptance criteria - [ ] An external monitor checks the health endpoint on a short interval - [ ] Sustained failures trigger an alert through at least one operator channel (email/webhook) - [ ] Recovery sends an all-clear notification - [ ] Alert thresholds avoid flapping on single transient failures
ryan-knowone commented 2026-07-03 13:32:47 +00:00 (Migrated from github.com)

Hi @manlycucumber — your acceptance criteria map well to a lightweight external monitor. A few options:

  • UptimeRobot or Better Uptime are the standard choices: health-endpoint checks, email/SMS/webhook alerts, recovery notifications, and threshold tuning to avoid flapping.

  • If you want something smaller and webhook-first, I work on sunwatch: add your health endpoint + webhook URL, and it pings every minute and alerts on down/up state changes. No account or KYC; paid per-monitor in USDC on Base after 3 free monitors. Probably overkill if you need SMS/email, but fits if you just want webhook recovery alerts.

Either way I'd start with a 1-minute interval and alert only after 2–3 consecutive failures to avoid flapping.

Hi @manlycucumber — your acceptance criteria map well to a lightweight external monitor. A few options: - [UptimeRobot](https://uptimerobot.com/) or [Better Uptime](https://betterstack.com/uptime) are the standard choices: health-endpoint checks, email/SMS/webhook alerts, recovery notifications, and threshold tuning to avoid flapping. - If you want something smaller and webhook-first, I work on [sunwatch](https://sunwatch.sunfamily.xyz): add your health endpoint + webhook URL, and it pings every minute and alerts on down/up state changes. No account or KYC; paid per-monitor in USDC on Base after 3 free monitors. Probably overkill if you need SMS/email, but fits if you just want webhook recovery alerts. Either way I'd start with a 1-minute interval and alert only after 2–3 consecutive failures to avoid flapping.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Directorium/Site#27
No description provided.