Health API
Liveness and readiness probe endpoints
You're viewing a development version of manager,
the latest released version is v1.4.1
Page not available in that version
The current page Health API doesn't exist in version v1.4.1 of the documentation for this product.
We can take you to the closest parent section instead: /docs/acd/components/manager/v1.4.1/api_guide/
Overview
The Health API provides endpoints for Kubernetes health probes and service health checking.
Base URL
https://<manager-host>/api/v1/health
Endpoints
GET /api/v1/health/alive
Liveness probe that indicates whether the service is running. Always returns 200 OK.
Request:
GET /api/v1/health/alive
Response (200):
{
"status": "Ok"
}
Use Case: Kubernetes liveness probe to determine if the pod should be restarted.
GET /api/v1/health/ready
Readiness probe that checks service readiness including downstream dependencies.
Request:
GET /api/v1/health/ready
Success Response (200):
{
"status": "Ok"
}
Failure Response (503):
{
"status": "Fail"
}
Use Case: Kubernetes readiness probe to determine if the pod should receive traffic. Returns 503 if any downstream dependencies (database, Kafka, Redis) are unavailable.
Kubernetes Configuration
Example Kubernetes probe configuration:
livenessProbe:
httpGet:
path: /api/v1/health/alive
port: 8080
initialDelaySeconds: 10
periodSeconds: 10
readinessProbe:
httpGet:
path: /api/v1/health/ready
port: 8080
initialDelaySeconds: 5
periodSeconds: 5
Next Steps
- Authentication API - User authentication
- Selection Input API - Key-value and list storage
- OpenAPI Specification - Complete API specification