Skip to main content

Health checks

Every Data Orchestrator service, whether it's an API service or not, exposes an HTTP endpoint /health, without versioning, on its HTTP port. By default, services use port 4000. /health is meant to be called frequently and reports the individual health state of a service. It will return 200 in case the service is healthy, or other errors in case the service is having issues. Among those issues, there might be failure in accessing RabbitMQ/RPC communications or failure in accessing the Database.

Health checks and Kubernetes​

The aforementioned health checks are integrated in Kubernetes, when using Data Orchestrator Operator, as LivenessProbe and ReadinessProbe. As such, health monitoring and forced restarts are automatically handled without the need for the administrator to integrate any additional logic.