Health Check in CDD
Health Check gives the ability to monitor the health of the Due Diligence application. This is useful not only to test the internal health of an application but also it’s external dependencies such as a third party API which Due Diligence application relies on to function correctly.
Microservices' health check helps to monitor the health of Due Diligence microservice APIs as classified below:
- API health check
- Database check
- Third-party API check
Monitor CDD
API Health Check
Due Diligence Microservices expose API health check endpoint to monitor the health of Microservice APIs.
Pattern: http://<host>:<port>/<context-root>/api/health/api
Sample: http://localhost:8004/ms-duediligence-api/api/v1.0.0/health/api/
Kubernetes Configuration
Follow the steps below to configure health check for Due Diligence Microservice in values.yaml and duediligence-configmap.yml (configurations are enabled by default), and set the className_getHealthCheck environment variable in API container to enable API health check.
Enabling Health Check for API Containerservice: duediligenceapi: type: LoadBalancer port: 8004
Enabling Health Check for API Containerdata:
#--- API Health Check ---
className_getHealthCheck: com.temenos.microservice.framework.core.health.GetHealthCheckImpl
Monitor CDD
API Health Check
Due Diligence Microservices expose API health check endpoint to monitor the health of Microservice APIs.
Pattern: http://<host>:<port>/<context-root>/api/health/api
Sample: http://localhost:8004/ms-duediligence-api/api/v1.0.0/health/api/
In this topic