Comprehensive readiness probe that checks the health of all application dependencies. This endpoint verifies database, cache, rate limiting, and vector store connectivity.
Detailed health check that verifies all application dependencies are operational. Checks the health of database, Redis cache, limit enforcement system, and Qdrant vector store.
Useful for container orchestration readiness probes.
Returns overall health status and individual component statuses.
Status Code: 200 OK
Response Body (Healthy):
{
"status": "healthy",
"components": [
{
"name": "database",
"status": "healthy",
"details": "Connection successful"
},
{
"name": "redis",
"status": "healthy",
"details": "Connection successful"
},
{
"name": "limit_enforcement",
"status": "healthy",
"details": "System operational"
},
{
"name": "qdrant",
"status": "healthy",
"details": "Connection successful"
}
]
}| Field | Type | Description |
|---|---|---|
status | string | Overall health status: "healthy", "degraded", or "unhealthy" |
components | array | Array of component health statuses |
components[].name | string | Component name |
components[].status | string | Component status: "healthy", "degraded", or "unhealthy" |
components[].details | string | Detailed status information (optional) |
The overall status is determined by component statuses:
healthy- All components are healthydegraded- At least one component is degraded, but none are unhealthyunhealthy- At least one component is unhealthy
- Name:
"database" - Checks: PostgreSQL connection and query execution
- Healthy: Connection successful
- Unhealthy: Connection timeout or error
- Name:
"redis" - Checks: Redis cache connectivity
- Healthy: Connection successful
- Unhealthy: Connection timeout or error
- Name:
"limit_enforcement" - Checks: Rate limiting system status
- Healthy: System operational
- Unhealthy: System unavailable
- Name:
"qdrant" - Checks: Vector store connectivity
- Healthy: Connection successful
- Unhealthy: Connection timeout or error
This endpoint is ideal for:
- Container readiness probes
- Dependency connectivity monitoring
- Comprehensive health monitoring
- Pre-deployment validation
readinessProbe:
httpGet:
path: /v1/health/details
port: 8000
initialDelaySeconds: 5
periodSeconds: 5Expected response time: < 500ms (includes all dependency checks)
The readiness endpoint can be integrated with:
- Prometheus - Health metrics collection
- Grafana - Dashboard visualization
- ELK Stack - Log aggregation
- Custom monitoring - Automated alerts
When one or more components are degraded but none are unhealthy:
{
"status": "degraded",
"components": [
{
"name": "database",
"status": "healthy",
"details": "Connection successful"
},
{
"name": "redis",
"status": "degraded",
"details": "High latency detected"
},
{
"name": "limit_enforcement",
"status": "healthy",
"details": "System operational"
},
{
"name": "qdrant",
"status": "healthy",
"details": "Connection successful"
}
]
}When one or more components are unhealthy:
{
"status": "unhealthy",
"components": [
{
"name": "database",
"status": "unhealthy",
"details": "Connection timeout"
},
{
"name": "redis",
"status": "healthy",
"details": "Connection successful"
},
{
"name": "limit_enforcement",
"status": "healthy",
"details": "System operational"
},
{
"name": "qdrant",
"status": "unhealthy",
"details": "Connection refused"
}
]
}