rcourtman 53029b08ea Make availability checks agree across Settings and Machines ...

Settings said "2 down" where Machines said "1 offline, 3 need
attention" for the same checks. Settings counted any failed latest
probe as down, while Machines and the alert engine count a check offline
only once it has failed its threshold number of times in a row.

Settings now classifies each check with the Machines status of its
resource when that is loaded, and otherwise reads the target the way the
availability poller does, so both pages report the same counts in the
same words. A check that is failing but not yet offline is amber, with
the threshold on hover.

The Machines table shows 24h uptime beside the latest result (it existed
only in the Fleet view), and only when most of the window had a
determinate answer, refreshing every five minutes. Failures read "3 in a
row" instead of "3/2", polling cadence moves to the widest tables, and
the duplicate Manage link is gone.

2026-10-05 05:31:04 +01:00

..

internal

Preserve the published 6.4.6 packet's release-line mapping

2026-10-02 21:15:35 +01:00

v6

Make availability checks agree across Settings and Machines

2026-10-05 05:31:04 +01:00

control_plane.json

Cut 6.5 and later releases from main

2026-10-04 18:37:43 +01:00

control_plane.schema.json

…