alertmanager/ui/app
Max Leonard Inden b3bb5dca80
Rework SilenceForm
* Restyle SilenceForm view
* Add validation to SilenceForm
* Redirect to new silence when editing expired one
2017-05-19 14:14:35 +02:00
..
src Rework SilenceForm 2017-05-19 14:14:35 +02:00
tests Add 'silenced' query param to /alerts endpoint 2017-05-17 18:59:20 +02:00
vendor Add Elm UI rewrite from github.com/stuartnelson3/am-ui with history 2017-03-24 17:48:50 +01:00
.gitignore Add Elm UI rewrite from github.com/stuartnelson3/am-ui with history 2017-03-24 17:48:50 +01:00
CONTRIBUTING.md Add CONTRIBUTING.md for front-end code 2017-03-31 17:49:50 +02:00
Makefile test: Introduce elm-test package 2017-04-25 12:03:02 +02:00
README.md Add CONTRIBUTING.md for front-end code 2017-03-31 17:49:50 +02:00
elm-package.json Switch to /alerts endpoint and restlye alerts list page 2017-05-02 09:46:20 +02:00
index.html Restyle SilenceList view and group by state 2017-05-11 11:30:36 +02:00
main.go Click alert matchers (#690) 2017-04-08 13:00:21 +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