alertmanager/ui/app
stuart nelson 4f8ef26b28 Update matching algorithm (#910)
* Test for consecutive chars throughout string

Previously, we were only testing for consecutive
characters at the beginning of the string. Now,
the entire string being compared is searched
through for a matching character, and then the
consecutive search starts.

We were seeing weird situations where the text
entered matched the last half of certain terms,
but because it wasn't, but because we only
searched from the start, results that probably
shouldn't have been the top suggestion were being
suggested too high on the list.

* Weight consecutive matches more highly

Bit of a guess, this seemed to give better results
for my small test case.

* bindata
2017-07-19 11:50:33 +02:00
..
src Update matching algorithm (#910) 2017-07-19 11:50:33 +02:00
tests Update matching algorithm (#910) 2017-07-19 11:50:33 +02:00
.gitignore
CONTRIBUTING.md Improve front-end build process 2017-07-06 13:43:10 +02:00
elm-package.json
favicon.ico
index.html
Makefile Improve front-end build process 2017-07-06 13:43:10 +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