Vendure exposes a /health endpoint on the server. It is a plain REST route which returns
{ "status": "ok" } as soon as the application is accepting HTTP requests.
The response is unconditional. /health does not check the database or any other dependency. It only
tells you that this process is running and serving HTTP, which is what a liveness probe needs.
Before v3.6.0, /health ran the strategies configured in systemOptions.healthChecks and returned a
503 if any of them failed. Since v3.6.0 those strategies are not executed. The strategy classes and
HealthCheckRegistryService will be removed in v4.0.0. Remove any custom strategies and set
healthChecks: [] to silence the startup warning. See #4441 for the reasoning.
Checking dependencies from the application health endpoint was removed on purpose. If /health failed
whenever the database was slow, an orchestrator would restart every instance at once, and restarting the
application cannot fix the database. Monitor dependencies with their own alerting and keep the
application probe shallow.
The worker can serve the same unconditional /health response. See the
for how to enable it.