This is the ThingsDB documentation for version v0, click here for the latest version!
http_status_port is set in the configuration file or the environment variable
/healthy are available.
These can be used for readiness and liveness requests.
/healthy check will respond with a
200 OK whenever possible and will never respond with an error. So only if no response is received in some reasonable amount of time, the node should be considered as unhealthy.
It is common to use the
/healthy check as liveness probe in environments like Kubernetes.
/healthy check there is also a
/ready check. This check responds with
200 OK if the node has one of the following status:
AWAY_SOON. With any other status, for example,
/ready check will respond with
503 Service Unavailable (NOK).
Since v0.9.20 ThingsDB will also respond with
200 OK to a
/ready request when all of the following conditions are met:
The following link will explain how to deploy ThingsDB in GKE (Google Kubernetes Engine) and can be used as an example for using the