Google Git
Sign in
gerrit / plugins / healthcheck / 06a1d9f5ffd9582e6f474f950f018f3c62594591
commit06a1d9f5ffd9582e6f474f950f018f3c62594591[log] [tgz]
authorLuca Milanesio <luca.milanesio@gmail.com>Mon Jan 14 16:49:55 2019 +0000
committerLuca Milanesio <luca.milanesio@gmail.com>Wed Jan 16 14:18:39 2019 +0000
tree1d9edba534683a885ea53d3130df475cb9ecc80b
parenta3b3a5c8fc60136120010124945be6a179a73571 [diff]
Implement ReviewDb health-check

Check if Gerrit is able to open a connection to ReviewDb
and execute a simple query on it.

Change-Id: I08184523670aad9f78dcbc2435424ec454ed2c5a
14 files changed
tree: 1d9edba534683a885ea53d3130df475cb9ecc80b
  1. src/
  2. BUILD
  3. LICENSE
  4. README.md
README.md

Plugin to verify the Gerrit health status

Allow having a single entry point to check the availability of the services that Gerrit exposes.

How to build

Clone or link this plugin to the plugins directory of Gerrit‘s source tree, and then run bazel build on the plugin’s directory.

Example:

git clone --recursive https://gerrit.googlesource.com/gerrit
git clone https://gerrit.googlesource.com/plugins/healthcheck
pushd gerrit/plugins && ln -s ../../healthcheck . && popd
cd gerrit && bazel build plugins/healthcheck

The output plugin jar is created in:

bazel-genfiles/plugins/healthcheck/healthcheck.jar

How to install

Copy the healthcheck.jar into the Gerrit's /plugins directory and wait for the plugin to be automatically loaded.

How to use

The healthcheck plugin exposes a single endpoint under its root URL and provides a JSON output of the Gerrit health status.

The HTTP status code returned indicates whether Gerrit is healthy (HTTP status 200) or has some issues (HTTP status 500).

The HTTP response payload is a JSON output that contains the details of the checks performed.

  • ts: epoch timestamp in millis of the test
  • elapsed: elapsed time in millis to perform the check
  • reviewdb: check that Gerrit can connect and query ReviewDb
  • projectslist: check that Gerrit can list projects
  • auth: check that Gerrit can authenticate users

Each check returns a JSON payload with the following information:

  • ts: epoch timestamp in millis of the individual check

  • elapsed: elapsed time in millis to complete the check

  • result: result of the health check

    • passed: the check passed successfully
    • failed: the check failed with an error
    • timeout: the check took too long and timed out

Example of a healthy Gerrit response:

GET /config/server/healthcheck~status

200 OK
Content-Type: application/json

{
  "ts": 139402910202,
  "elapsed": 100,
  "reviewdb": {
    "ts": 139402910202,
    "elapsed": 50,
    "result": "passed"
  },
  "projectslist": {
    "ts": 139402910202,
    "elapsed": 100,
    "result": "passed"
  },
  "auth": {
    "ts": 139402910202,
    "elapsed": 80,
    "result": "passed"
  }
}

Example of a Gerrit instance with the projects list timing out:

GET /config/server/healthcheck~status

500 ERROR
Content-Type: application/json

{
  "ts": 139402910202,
  "elapsed": 100,
  "reviewdb": {
    "ts": 139402910202,
    "elapsed": 50,
    "result": "passed"
  },
  "projectslist": {
    "ts": 139402910202,
    "elapsed": 100,
    "result": "timeout"
  },
  "auth": {
    "ts": 139402910202,
    "elapsed": 80,
    "result": "passed"
  }
}