# 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](https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/#liveness-probe). ### Readiness The `/readyz` endpoint indicates when the collector is ready to receive data, commonly used in the [Kubernetes Readiness probe](https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/#readiness-probe). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.elastiflow.com/flowcoll/overview/liveness_readiness.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.