Readiness probe
Requires a working database pool. FIPS state and audit queue depth are reported but do not by themselves fail the probe: a deep queue spills to the write-ahead log rather than losing records, and removing the node from rotation would only push load onto its peers.
The detailed body is returned only when the installation sets
EXPOSE_HEALTH_DETAIL, which it does not outside local environments,
because this endpoint answers before authentication. Otherwise only
status is present.
Response
Ready for traffic: the database pool answered. With
EXPOSE_HEALTH_DETAIL off, which is the production setting, the
body is only {"status": "ready"}.
Only status is present unless the installation exposes the detailed
body.
ready, unavailable The license in force on this node.
Incremented by every security-sensitive mutation. Each node polls it and treats cached decisions stamped with an older value as a miss, which is what makes a revocation take effect cluster-wide at once.