BigW Consortium Gitlab

health_check.md 2.31 KB
Newer Older
1
# Health Check
2 3

>**Note:** This feature was [introduced][ce-3888] in GitLab 8.8.
4 5 6 7 8

GitLab provides a health check endpoint for uptime monitoring on the `health_check` web
endpoint. The health check reports on the overall system status based on the status of
the database connection, the state of the database migrations, and the ability to write
and access the cache. This endpoint can be provided to uptime monitoring services like
9
[Pingdom][pingdom], [Nagios][nagios-health], and [NewRelic][newrelic-health].
10 11 12

## Access Token

13
An access token needs to be provided while accessing the health check endpoint. The current
14
accepted token can be found on the `admin/health_check` page of your GitLab instance.
15 16 17

![access token](img/health_check_token.png)

18
The access token can be passed as a URL parameter:
19

20 21 22
```
https://gitlab.example.com/health_check.json?token=ACCESS_TOKEN
```
23

24
or as an HTTP header:
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

```bash
curl -H "TOKEN: ACCESS_TOKEN" https://gitlab.example.com/health_check.json
```

## Using the Endpoint

Once you have the access token, health information can be retrieved as plain text, JSON,
or XML using the `health_check` endpoint:

- `https://gitlab.example.com/health_check?token=ACCESS_TOKEN`
- `https://gitlab.example.com/health_check.json?token=ACCESS_TOKEN`
- `https://gitlab.example.com/health_check.xml?token=ACCESS_TOKEN`

You can also ask for the status of specific services:

- `https://gitlab.example.com/health_check/cache.json?token=ACCESS_TOKEN`
- `https://gitlab.example.com/health_check/database.json?token=ACCESS_TOKEN`
- `https://gitlab.example.com/health_check/migrations.json?token=ACCESS_TOKEN`

45 46
For example, the JSON output of the following health check:

47 48
```bash
curl -H "TOKEN: ACCESS_TOKEN" https://gitlab.example.com/health_check.json
49 50 51 52 53
```

would be like:

```
54 55 56 57 58
{"healthy":true,"message":"success"}
```

## Status

59 60
On failure, the endpoint will return a `500` HTTP status code. On success, the endpoint
will return a valid successful HTTP status code, and a `success` message. Ideally your
61 62 63 64 65 66
uptime monitoring should look for the success message.

[ce-3888]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3888
[pingdom]: https://www.pingdom.com
[nagios-health]: https://nagios-plugins.org/doc/man/check_http.html
[newrelic-health]: https://docs.newrelic.com/docs/alerts/alert-policies/downtime-alerts/availability-monitoring