2223da2c30
When users start Alertmanager with `--cluster.listen-address=`, the cluster will not be initialized, hence api.peer will be `nil`. So far this would result in a nil pointer dereference by the API v2 accessing the api.peer field. With this patch, api v2 skips populating the peers array, sets the name to an empty string and the status to "disabled" in case `api.peer` is nil. Signed-off-by: Max Leonard Inden <IndenML@gmail.com> |
||
|---|---|---|
| .. | ||
| lib | ||
| src | ||
| tests | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| Makefile | ||
| README.md | ||
| elm.json | ||
| favicon.ico | ||
| index.html | ||
README.md
Alertmanager UI
This is a re-write of the Alertmanager UI in elm-lang.
Usage
Filtering on the alerts page
By default, the alerts page only shows active (not silenced) alerts. Adding a query string containing the following will additionally show silenced alerts.
http://alertmanager/#/alerts?silenced=true
The alerts page can also be filtered by the receivers for a page. Receivers are configured in Alertmanager's yaml configuration file.
http://alertmanager/#/alerts?receiver=backend
Filtering based on label matchers is available. They can easily be added and modified through the UI.
http://alertmanager/#/alerts?filter=%7Bseverity%3D%22warning%22%2C%20owner%3D%22backend%22%7D
These filters can be used in conjunction.
Filtering on the silences page
Filtering based on label matchers is available. They can easily be added and modified through the UI.
http://alertmanager/#/silences?filter=%7Bseverity%3D%22warning%22%2C%20owner%3D%22backend%22%7D
Note on filtering via label matchers
Filtering via label matchers follows the same syntax and semantics as Prometheus.
A properly formatted filter is a set of label matchers joined by accepted matching operators, surrounded by curly braces:
{foo="bar", baz=~"quu.*"}
Operators include:
=!==~!~
See the official documentation for additional information: https://prometheus.io/docs/querying/basics/#instant-vector-selectors