You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(orb): add fleet-wide instance health aggregation
The existing readiness check (/health, /ready) is per-instance only and
never leaves the instance -- there was no way for an operator centrally
managing many self-hosted instances to see which ones are actually up.
Threads readiness() (the exact same check /ready already answers with)
into the hourly Orb telemetry export, riding the same request even in a
tick with nothing new to export -- no second, parallel health-check
mechanism. The central ingest handler accepts this as an optional health
field, relaxing the "empty events" rejection only when a health signal
accompanies it, and persists it to two new orb_instances columns
(healthy, health_reported_at) via a COALESCE-based upsert: an
outcome-only export from a build that hasn't upgraded yet never
overwrites a previously-reported status with null, and never looks
healthy just because the instance is otherwise active.
A new getFleetHealthSummary() aggregates healthy/unhealthy/unknown counts
across registered instances, with a staleness window (unresponsive reads
as unknown, not stuck on its last-known state) -- surfaced on the
operator dashboard as "Instance status", named distinctly from the
existing "Fleet health" card (gate-calibration quality, an unrelated
concept that happens to share the word "health").
Closes#4933
0 commit comments