Skip to content

Health module ​

Current status ​

services/health is listed in go.work and contains a module manifest, Makefile, and Dockerfile, but no Go source. It is not composed as a functional independent health service. The current API server defines its own /healthz handler in services/api/cmd/server.

The documentation container has a separate Caddy /healthz endpoint returning OK and uses it for its container healthcheck. That confirms the static server responds; it does not check the API, PostgreSQL, or RabbitMQ.

No Go package page is generated for this module. If it gains code, workspace package discovery will include it automatically. Keep deployment documentation and the API guide aligned with any future readiness/liveness changes rather than claiming this scaffold supplies continuous dependency health monitoring.

Documentation follows the source. Planned contracts are marked explicitly.