krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-09-28 23:48:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

Document Kubernetes healthz, readyz and livez endpoints

Browse Source
This commit is contained in:
timvisee
2023-09-07 14:17:26 +02:00
parent bd2a0d784f
commit 07b400b7f4
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/guides/monitoring.md
+16
View File
@@ -51,3 +51,19 @@ There are also some metrics which are exposed in distributed mode only.
| cluster_commit | counter | Index of last committed (finalized) operation cluster peer is aware of | | cluster_commit | counter | Index of last committed (finalized) operation cluster peer is aware of |
| cluster_pending_operations_total | gauge | Total number of pending operations for cluster peer | | cluster_pending_operations_total | gauge | Total number of pending operations for cluster peer |
| cluster_voter | gauge | Whether the cluster peer is a voter or learner | | cluster_voter | gauge | Whether the cluster peer is a voter or learner |
## Kubernetes health endpoints
*Available as of v1.5.0*
Qdrant exposes three endpoints, namely `/healthz`, `/livez` and `/readyz`, to
indicate the current status of the Qdrant server.
These currently provide the most basic status response, returning HTTP 200 if
Qdrant is started and ready to be used.
Regardless of whether an [API key](../security#authentication) is configured,
the endpoints are always accessible.
You can read more about Kubernetes health endpoints
[here](https://kubernetes.io/docs/reference/using-api/health-checks/).