Health Check
A health check is a lightweight HTTP endpoint (such as /health or /ready) in microservices used to determine whether a service process is alive and whether it is ready. It does not involve business logic and is commonly used for liveness and readiness probes in container orchestration.
Timeline (last 90 days)
A health check route is usually a lightweight HTTP endpoint (such as `/health` or `/ready`) used to quickly determine whether the service process is alive and ready to receive traffic; it does not involve business logic and does not verify whether downstream dependencies are available.
A health check that depends on the database amplifies a brief database hiccup into a restart of the entire service; a health check should only prove that the process is handling requests
All Facts (2)
A health check route is usually a lightweight HTTP endpoint (such as `/health` or `/ready`) used to quickly determine whether the service process is alive and ready to receive traffic; it does not involve business logic and does not verify whether downstream dependencies are available.
50%UnverifiedA health check that depends on the database amplifies a brief database hiccup into a restart of the entire service; a health check should only prove that the process is handling requests
50%