Commit graph

2 commits

Author SHA1 Message Date
7fb11211d7
status: don't call a site down if it never answered
All checks were successful
Build and Deploy to Production / test (push) Successful in 17s
Build and Deploy to Production / build (push) Successful in 48s
Build and Deploy to Production / deploy (push) Successful in 33s
DataLine NORD showed "not answering" from its first round. Its only
target, JustHost's "Moscow, DataLine" test IP, is listed but doesn't
answer from abroad at all, like most of JustHost's Russian test IPs
(only St Petersburg does). The control hosts sit on other networks, so
they couldn't flag it.

Mark a site down only if its targets answered at some point in the
24-hour window; one that never answered reads as unknown.

Assisted-by: Claude:opus-5-5
2026-10-18 10:43:20 +04:00
1a5506c77d
Add a public reachability status page
All checks were successful
Build and Deploy to Production / test (push) Successful in 18s
Build and Deploy to Production / build (push) Successful in 49s
Build and Deploy to Production / deploy (push) Successful in 33s
asxpio now probes public hosts tied to each datacenter once a minute
and stores 5-minute rows (bingo_monitor_* tables, granted to the
read-only bingo role). Show them: /:locale/status lists every monitored
site with its current state and a 24-hour bar, /status.json has the
same data, and monitored datacenter pages get a small block.

A site is down only when nothing answered for two buckets. Everything
reads as unknown when the worker is stale or fewer than half of the
control hosts in Russia answer, since probes run from Finland and
filtering can look like an outage. The page says plainly that this is
not an incident record.

Refresh test/schema.sql for asxpio's migration 017.

Assisted-by: Claude:opus-5-5
2026-10-18 10:33:52 +04:00