feat(health): worker-exe presence and bounded Galaxy SQL readiness checks (mxaccessgw#206)
Adds WorkerExecutableHealthCheck (configured worker .exe exists) and GalaxySqlHealthCheck (IGalaxyRepository.TestConnectionAsync bounded by a 5 s TimeProvider-driven timeout). Both are tagged ready only, never live, so an outage takes the node out of rotation without triggering a restart; sessions stay on the active tier so zero sessions is still healthy for Overview. Registrations move into AddGatewayHealthChecks() so the tier tagging is unit-tested. LDAP is not added (sign-in already surfaces bind failures). docs/Diagnostics.md lists the two new checks. Claude-Session: https://claude.ai/code/session_01GT67AEHd2Acv1YPwGfXEoV
This commit is contained in:
@@ -223,6 +223,8 @@ The shared `ZB.MOM.WW.Health` package maps three endpoints — `/healthz` (live)
|
||||
| Check | Endpoint tier | Fails when |
|
||||
|---|---|---|
|
||||
| `auth-store` | `ready` | The SQLite auth store cannot be opened. Every gRPC call authenticates against it, so its reachability genuinely gates whether the process should receive traffic. |
|
||||
| `worker-executable` | `ready` | The configured `MxGateway:Worker:ExecutablePath` does not resolve to an existing file, so every session start would fail with `ExecutableNotFound`. |
|
||||
| `galaxy-sql` | `ready` | The Galaxy Repository SQL ping fails or exceeds its 5 s bound. Never `live`: an outage takes the node out of rotation but a restart cannot fix it. |
|
||||
| `mxaccess-sessions` | `active` | Sessions exist and their workers have faulted. Reports `total` / `ready` / `faulted` / `starting` / `closing` as entry `data`. |
|
||||
|
||||
**Zero sessions is Healthy, and the tier choice follows from that.** The gateway opens an MXAccess
|
||||
|
||||
Reference in New Issue
Block a user