alertmanager/ui/app
Paul Gier c834a991c6 set ELM_HOME for the elm-env container
The ELM_HOME variable needs to be set to the mounted volume
directory when building to prevent permissions errors caused
by using root as the default home dir.

Signed-off-by: Paul Gier <pgier@redhat.com>
2019-03-11 10:45:45 -05:00
..
lib Use elm reactor for dev assets (#1133) 2017-12-10 21:59:15 +01:00
src Make the silence preview show also muted alerts 2019-03-01 14:15:53 +01:00
tests Upgrade Alertmanager UI to Elm 0.19 (#1539) 2018-09-06 18:08:51 +02:00
.gitignore
CONTRIBUTING.md Add signed off to commit (#1766) 2019-02-25 11:04:42 +01:00
Makefile set ELM_HOME for the elm-env container 2019-03-11 10:45:45 -05:00
README.md Add CONTRIBUTING.md for front-end code 2017-03-31 17:49:50 +02:00
elm.json ui: Move /status & /silences to API v2 2018-11-15 13:24:26 +01:00
favicon.ico Add favicon (#839) 2017-06-01 10:13:20 +02:00
index.html Upgrade Alertmanager UI to Elm 0.19 (#1539) 2018-09-06 18:08:51 +02:00

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