You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hosting/logging-monitoring/monitoring.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,19 +6,27 @@ contentType: howto
6
6
7
7
# Monitoring
8
8
9
-
There are two API endpoints you can call to check the status of your instance: `/healthz` and `/metrics`.
9
+
There are three API endpoints you can call to check the status of your instance: `/healthz`, `healthz/readiness`, and `/metrics`.
10
10
11
11
<!-- vale off -->
12
-
## healthz
12
+
## healthz and healthz/readiness
13
13
<!-- vale on -->
14
-
The `/healthz` endpoint returns a standard HTTP status code. 200 indicates the instance is reachable. It's available for both self-hosted and Cloud users.
14
+
The `/healthz` endpoint returns a standard HTTP status code. 200 indicates the instance is reachable. It doesn't indicate DB status. It's available for both self-hosted and Cloud users.
15
15
16
16
Access the endpoint:
17
17
18
18
```
19
19
<your-instance-url>/healthz
20
20
```
21
21
22
+
The `/healthz/readiness` endpoint is similar to the `/healthz` endpoint, but it returns a HTTP status code of 200 if the DB is connected and migrated and therefore the instance is ready to accept traffic.
0 commit comments