Liveness probe — is the process alive? — GET /health/live
Liveness probe — is the process alive?
Kubernetes liveness probe. Returns 200 as long as the process is running and the event loop is responsive. Never checks external dependencies — a database outage must NOT restart the pod.
Endpoint: GET /health/live
Authentication: No access token or API key is needed.
Parameters
Section titled “Parameters”This endpoint takes no parameters.
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | Not documented (application/json) |
Response fields not documented. The API specification does not describe the body of every response this endpoint returns, so this page cannot list those fields. The body is not empty. To see it, call the endpoint on your own installation. All endpoints with undocumented responses.
Statuses not listed here are explained in Errors and retries.
More details
Section titled “More details”- Group: Health
- Operation ID:
liveness_health_live_get - Source code:
backend/app/routers/health.py, line 235 - Specification: OpenAPI JSON