2019-09-14 23:59:05 +00:00
|
|
|
# gatus
|
|
|
|
|
2020-04-10 21:19:59 +00:00
|
|
|
![build](https://github.com/TwinProduction/gatus/workflows/build/badge.svg?branch=master)
|
2019-09-14 23:59:05 +00:00
|
|
|
[![Docker pulls](https://img.shields.io/docker/pulls/twinproduction/gatus.svg)](https://cloud.docker.com/repository/docker/twinproduction/gatus)
|
2019-09-04 23:37:13 +00:00
|
|
|
|
2019-09-14 23:25:59 +00:00
|
|
|
A service health dashboard in Go that is meant to be used as a docker
|
|
|
|
image with a custom configuration file.
|
2019-09-11 01:05:57 +00:00
|
|
|
|
2019-11-11 21:15:35 +00:00
|
|
|
Live example: https://status.twinnation.org/
|
|
|
|
|
2019-09-11 01:05:57 +00:00
|
|
|
|
2019-09-09 01:07:08 +00:00
|
|
|
## Usage
|
2019-09-04 23:37:13 +00:00
|
|
|
|
2020-03-08 22:16:39 +00:00
|
|
|
By default, the configuration file is expected to be at `config/config.yaml`.
|
|
|
|
|
|
|
|
You can specify a custom path by setting the `GATUS_CONFIG_FILE` environment variable.
|
|
|
|
|
2020-04-15 00:13:06 +00:00
|
|
|
Here's a simple example:
|
|
|
|
|
2019-09-04 23:37:13 +00:00
|
|
|
```yaml
|
2019-11-16 20:49:06 +00:00
|
|
|
metrics: true # Whether to expose metrics at /metrics
|
2019-09-04 23:37:13 +00:00
|
|
|
services:
|
2019-09-09 01:07:08 +00:00
|
|
|
- name: twinnation # Name of your service, can be anything
|
2020-04-06 22:58:13 +00:00
|
|
|
url: https://twinnation.org/health
|
2020-04-10 20:34:20 +00:00
|
|
|
interval: 15s # Duration to wait between every status check (default: 10s)
|
2019-09-04 23:37:13 +00:00
|
|
|
conditions:
|
2020-04-12 03:14:20 +00:00
|
|
|
- "[STATUS] == 200" # Status must be 200
|
2020-04-15 00:13:06 +00:00
|
|
|
- "[BODY].status == UP" # The json path "$.status" must be equal to UP
|
2020-04-12 03:14:20 +00:00
|
|
|
- "[RESPONSE_TIME] < 300" # Response time must be under 300ms
|
2020-04-15 00:13:06 +00:00
|
|
|
- name: example
|
2020-04-12 03:17:31 +00:00
|
|
|
url: https://example.org/
|
|
|
|
interval: 30s
|
2019-09-09 01:07:08 +00:00
|
|
|
conditions:
|
2019-12-04 22:27:27 +00:00
|
|
|
- "[STATUS] == 200"
|
2019-09-09 01:07:08 +00:00
|
|
|
```
|
|
|
|
|
2019-12-04 22:27:27 +00:00
|
|
|
Note that you can also add environment variables in the your configuration file (i.e. `$DOMAIN`, `${DOMAIN}`)
|
|
|
|
|
2019-09-09 01:07:08 +00:00
|
|
|
|
2020-04-15 00:13:06 +00:00
|
|
|
### Configuration
|
|
|
|
|
2020-04-16 01:55:10 +00:00
|
|
|
| Parameter | Description | Default |
|
2020-04-15 00:13:06 +00:00
|
|
|
| ----------------------- | ------------------------------------------------------ | -------------- |
|
2020-04-16 01:55:10 +00:00
|
|
|
| `metrics` | Whether to expose metrics at /metrics | `false` |
|
|
|
|
| `services[].name` | Name of the service. Can be anything. | Required `""` |
|
|
|
|
| `services[].url` | URL to send the request to | Required `""` |
|
|
|
|
| `services[].conditions` | Conditions used to determine the health of the service | `[]` |
|
|
|
|
| `services[].interval` | Duration to wait between every status check | `10s` |
|
|
|
|
| `services[].method` | Request method | `GET` |
|
|
|
|
| `services[].body` | Request body | `""` |
|
|
|
|
| `services[].headers` | Request headers | `{}` |
|
2020-04-15 00:13:06 +00:00
|
|
|
|
|
|
|
|
2020-04-10 20:34:20 +00:00
|
|
|
### Conditions
|
|
|
|
|
|
|
|
Here are some examples of conditions you can use:
|
|
|
|
|
2020-04-12 23:51:28 +00:00
|
|
|
| Condition | Description | Passing values | Failing values |
|
2020-04-11 02:56:38 +00:00
|
|
|
| ------------------------------------- | ----------------------------------------- | ------------------------ | ----------------------- |
|
|
|
|
| `[STATUS] == 200` | Status must be equal to 200 | 200 | 201, 404, 500 |
|
|
|
|
| `[STATUS] < 300` | Status must lower than 300 | 200, 201, 299 | 301, 302, 400, 500 |
|
|
|
|
| `[STATUS] <= 299` | Status must be less than or equal to 299 | 200, 201, 299 | 301, 302, 400, 500 |
|
|
|
|
| `[STATUS] > 400` | Status must be greater than 400 | 401, 402, 403, 404 | 200, 201, 300, 400 |
|
|
|
|
| `[RESPONSE_TIME] < 500` | Response time must be below 500ms | 100ms, 200ms, 300ms | 500ms, 1500ms |
|
|
|
|
| `[BODY] == 1` | The body must be equal to 1 | 1 | literally anything else |
|
2020-04-12 23:54:33 +00:00
|
|
|
| `[BODY].data.id == 1` | The jsonpath `$.data.id` is equal to 1 | `{"data":{"id":1}}` | literally anything else |
|
2020-04-15 00:13:06 +00:00
|
|
|
| `[BODY].data[0].id == 1` | The jsonpath `$.data[0].id` is equal to 1 | `{"data":[{"id":1}]}` | literally anything else |
|
2020-04-12 23:51:28 +00:00
|
|
|
|
|
|
|
**NOTE**: `[BODY]` with JSON path (i.e. `[BODY].id == 1`) is currently in BETA. For the most part, the only thing that doesn't work is arrays.
|
2020-04-10 20:34:20 +00:00
|
|
|
|
|
|
|
|
2019-10-28 01:17:55 +00:00
|
|
|
## Docker
|
|
|
|
|
|
|
|
Building the Docker image is done as following:
|
2019-09-09 01:07:08 +00:00
|
|
|
|
|
|
|
```
|
2019-10-28 01:17:55 +00:00
|
|
|
docker build . -t gatus
|
2019-09-09 01:07:08 +00:00
|
|
|
```
|
2019-09-14 23:25:59 +00:00
|
|
|
|
2019-10-28 01:17:55 +00:00
|
|
|
You can then run the container with the following command:
|
2019-09-14 23:25:59 +00:00
|
|
|
|
2019-10-28 01:17:55 +00:00
|
|
|
```
|
|
|
|
docker run -p 8080:8080 --name gatus gatus
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
## Running the tests
|
2019-09-14 23:25:59 +00:00
|
|
|
|
|
|
|
```
|
2019-10-28 01:17:55 +00:00
|
|
|
go test ./... -mod vendor
|
2019-09-14 23:25:59 +00:00
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
## Using in Production
|
|
|
|
|
|
|
|
See the [example](example) folder.
|