Struct HealthRegistry 

pub struct HealthRegistry { /* private fields */ }

Global health registry singleton.

Modules register health check callbacks at construction. The registry aggregates all component statuses to determine overall service health.

Thread Safety

The registry uses Mutex<Vec<_>> for registration (infrequent, at init time) and read access (health checks). For the typical DFE app with 3-8 registered components, lock contention is negligible.

Implementations

impl HealthRegistry

pub fn register( name: impl Into<String>, check: impl Fn() -> HealthStatus + Send + Sync + 'static, )

Register a health check callback.

Called by modules at construction time. The callback is invoked each time health is queried, so it should be cheap (e.g., read an AtomicBool or check a cached state).

Duplicate Names

Multiple components may register with the same name. Each registration is independent — the registry does not deduplicate.

pub fn is_healthy() -> bool

Check if ALL components are healthy.

Returns true if the registry is empty (vacuously true) or every registered component reports HealthStatus::Healthy.

pub fn is_ready() -> bool

Check if the service is ready to receive traffic.

Ready means no component is HealthStatus::Unhealthy. Degraded components are acceptable — the service can still serve requests, just with reduced capability.

Returns true if the registry is empty (vacuously true).

pub fn components() -> Vec<(String, HealthStatus)>

Get per-component health status.

Returns a snapshot of all registered components and their current status. Useful for detailed health endpoints.

pub fn to_json() -> Value

Get a JSON representation of the health state.

Suitable for a /health/detailed endpoint response.