List of Kavmon checks in the "dependency_check" group¶
Checks in this group validate that application dependencies are available. These checks will be mainly used as dependency checks in k8s probes.
Note: These checks are run as part of services within DataRobot starting up automatically. As such, there is no corresponding kavmon kubernetes cron job that is scheduled to execute these checks like there are for the other check groups in this document.
"Mongo Dependency Check"
The check opens a connection to Mongo and issues ping admin command.
Returns unhealthy if:
- The value of ok from the response is 0
- Any exception is thrown while executing the ping command.
"Postgres Dependency Check"
The check opens a connection to Postgres and executes a sample query.
Returns unhealthy if:
- Invalid Postgres DSN was provided.
- Any exception is thrown while executing the check.
- Query result has no content.
"Check Internal API K8s Service"
The check attempts to open a socket connection against the Internal API k8s service.
Returns unhealthy if:
- The connection towards the
Internal APIk8s service was unsuccessful after the configured time threshold (set throughAM_INTERNAL_API_K8S_SERVICE_TIMEOUTenv var). - Environment variable
AM_INTERNAL_API_K8S_SERVICEwas not set correctly (should match regexhttps?://(?P<svc_host>.*):(?P<svc_port>\d+)\/?.*)
"Check mmqueue K8s Service"
The check attempts to open a socket connection against the mmqueue k8s service.
Returns unhealthy if:
- The connection towards the
mmqueuek8s service was unsuccessful after the configured time threshold (set throughAM_MMQUEUE_K8S_SERVICE_TIMEOUTenv var). - Environment variable
AM_MMQUEUE_K8S_SERVICEwas not set correctly (should match regexhttps?://(?P<svc_host>.*):(?P<svc_port>\d+)\/?.*)