summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCody West <cwest@gitlab.com>2019-01-11 19:37:55 -0600
committerCody West <cwest@gitlab.com>2019-01-11 19:37:55 -0600
commite1f258e6edc71e72b7e3694781eceddf5fc13bb5 (patch)
tree499ae44111036446d20a8e60e3fea1bad0599d16
parentd013362f018fca7c1156df9987d3dd138a18e26d (diff)
downloadgitlab-ce-docs-health-check-typo.tar.gz
Fix linting issuesdocs-health-check-typo
See: https://docs.gitlab.com/ee/development/documentation/#linting
-rw-r--r--doc/user/admin_area/monitoring/health_check.md9
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/user/admin_area/monitoring/health_check.md b/doc/user/admin_area/monitoring/health_check.md
index 8d859451297..f2d4e31d093 100644
--- a/doc/user/admin_area/monitoring/health_check.md
+++ b/doc/user/admin_area/monitoring/health_check.md
@@ -28,12 +28,11 @@ With default whitelist settings, the probes can be accessed from localhost:
- `http://localhost/-/readiness`
- `http://localhost/-/liveness`
-
The first endpoint, `/-/health`, only checks whether the application server is running. It does
-not verify the database or other services are running. A successful response will return
a 200 status code with the following message:
-```
+```text
GitLab OK
```
@@ -41,7 +40,7 @@ The readiness and liveness probes will provide a report of system health in JSON
Readiness example output:
-```
+```json
{
"queues_check" : {
"status" : "ok"
@@ -63,7 +62,7 @@ Readiness example output:
Liveness example output:
-```
+```json
{
"cache_check" : {
"status" : "ok"
@@ -102,7 +101,7 @@ accepted token can be found under the **Admin area ➔ Monitoring ➔ Health che
The access token can be passed as a URL parameter:
-```
+```text
https://gitlab.example.com/-/readiness?token=ACCESS_TOKEN
```