Skip to main content
This page covers the operational HTTP probes /health, /readyz, and /version. Orchestrators such as Kubernetes use them to decide when a service is alive, when it can receive traffic, and which build it runs. Paths, ports, and response bodies differ per service. See the per-service coverage table below.

The probe endpoints

The /readyz response body

/readyz returns a JSON document describing overall readiness and each dependency check.
Which checks turn the response into HTTP 503, and whether a degraded check does, differs per service.

Per-service coverage

The table lists default ports and the path deviations.
Ports are compose/.env.example defaults and can be overridden per deployment. See Default network ports. Varies marks a service whose default port depends on deployment configuration.