Liveness & Readiness

NetObserv provides liveness and readiness endpoints for use when deploying within a Kubernetes environment.

Liveness

The /livez endpoint is provided to determine the health status of the collector. This is commonly used to restart a container if the service becomes non-operational. The endpoint will return an HTTP status code of 200 and 500, when the collector is fully operational or when the collector is down and can not send data to the outputs respectively. Commonly used in the Kubernetes Liveness probe.

Readiness

The /readyz endpoint indicates when the collector is ready to receive data, commonly used in the Kubernetes Readiness probe.