2cf38e4c2e
Infer path from Navigation.Location Build uses template, local dev uses elm-reactor Remove unneeded local dev go server Add script.js make target Compiles and uglifies script.js Before: ~570kb After: ~170kb Bootstrap loading state Add trailing slash via JS & add routePrefix console param Add Javascript script tag to `index.html` which adds a trailing slash to the url pathname if none is present. This is done to ensure assets like `script.js` are loaded properly. Example without patch: If the pathname is "mxinden.com/alertmanager" the browser will try to download the `script.js` asset from "mxinden.com/script.js". This request will fail. Example with patch: If the pathname is "mxinden.com/alertmanager", Javascript redirects the browser to "mxinden.com/alertmanager/" and then the `script.js` asset will be downloaded from "mxinden.com/alertmanager/script.js". This request will succeed. Add `-web.route-prefix` as a console parameter. This configures a Prefix for the internal routes of web endpoints. Defaults to path of -web.external-url like in *Prometheus*. Trim slashes off of route prefix and add one slash at the beginning. Make sure route prefix is not empty or just a slash before prefixing router. |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| elm-package.json | ||
| favicon.ico | ||
| index.html | ||
| Makefile | ||
| 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