alertmanager/ui
Corentin Chary dd75201f1c Add /-/ready based on mesh status (#1209)
* Wait for the gossip to settle before sending notifications

See #1209 for details.

As an heuristic for mesh readyness, try to see if
the mesh looks stable (the number of peers isn't changing too much).
This implementation always mark the altermanager as ready after a maximum of 60s.

This adds one new flags to control this behavior:
```
      --cluster.settle-timeout=60s  mesh settling timeout. Do not wait more than this duration on startup.
```

It also adds `/-/ready` which always return 200 (in order to make it clear
that we are ready as soon as we can receive requests).

The mesh status is exposed in `/api/v1/status` and visible on `/#/status`.

* cluster: fix typos and base interval on gossipInterval
2018-03-02 15:45:21 +01:00
..
app Add /-/ready based on mesh status (#1209) 2018-03-02 15:45:21 +01:00
bindata.go Add /-/ready based on mesh status (#1209) 2018-03-02 15:45:21 +01:00
Dockerfile Fix external web url (#836) 2017-06-07 22:38:39 +02:00
web.go Add /-/ready based on mesh status (#1209) 2018-03-02 15:45:21 +01:00