Health Checks

@connectum/healthcheck implements the gRPC Health Checking Protocol and can expose HTTP endpoints for platform probes. The application owns status transitions; the protocol only reports them.

The application owns transitions. /healthz, /health and /readyz report the same aggregate state. Different liveness and readiness semantics require application-owned checks; changing the path name does not create another state.

With the healthcheck imports and your routes in scope:

const server = createServer({
  services: [routes],
  protocols: [Healthcheck({ httpEnabled: true })],
});

server.on('ready', () => {
  healthcheckManager.update(ServingStatus.SERVING);
});

Choose the owning guide

Start with the health protocol or Kubernetes probes.

Exact health tasks and API

Need	Canonical destination
Configure protocol options, HTTP paths, status semantics, components, or dependency state	Health protocol
Configure Kubernetes HTTP/gRPC probes and termination timing	Kubernetes integration
Coordinate drain hooks and the global shutdown deadline	Graceful shutdown
Find an exact manager or protocol symbol	@connectum/healthcheck API

Readiness means the process can accept useful work; liveness means it should not be restarted. During shutdown, mark the service not serving before draining traffic. Worker-only processes with services: [] should register an application component in the manager so /healthz has an explicit readiness source; the protocol guide owns that pattern.

Use the health protocol guide for installation and configuration.