Alert dashboard for Prometheus Alertmanager
This release fixes issues with Host
header and basic auth headers in proxy mode found and fixed by @svenmueller.
All merged pull requests:
Action needed: breaking changes in configuration handling.
This release adds a config file support, which allows for configuration of advanced options that would be hard to work with if expressed only via cli flags and/or environment variables. An effort was made to keep all old env variables still working, but they are considered legacy and will be removed in the next release. There is no compatibility with old cli flags.
With new config file it's now possible to use new features:
See docs/CONFIGURATION.md for details on all changes to configuration handling. There is also an example config file, see docs/example.yaml.
All merged pull requests:
This release introduces big changes in the way web assets are managed, npm and webpack are now used for that. Please report any bugs that break unsee in your browser.
New configuration options were added:
ANNOTATIONS_VISIBLE
ANNOTATIONS_HIDDEN
ANNOTATIONS_DEFAULT_HIDDEN
KEEP_LABELS
See the documentation for details.
All merged pull requests:
Bugfix release that fixes issue with browser cache causing errors with lru.js
.
All merged pull requests:
This release includes support for collecting alerts from multiple Alertmanager instances.
ALERTMANAGER_URI
was renamed to ALERTMANAGER_URIS
and the syntax is now different. Previously the value would be simply the URI of the Alertmanager instance, now it's a list of ${name}:${uri}
. Example: ALERTMANAGER_URI=https://example.com
needs to be updated to ALERTMANAGER_URIS=default:https://example.com
, default
will then be the name of the Alertmanager instance used which can be used in @alertmanager
filter.
For users who want to collect alerts from multiple sources example would be: ALERTMANAGER_URIS=am1:https://am1.example.com am2:https://am2.example.com
, @alertmanager=am1
and @alertmanager=am2
filters would allow to filter alerts based on the instances they were collected from.
If the same alert (same means having identical set of labels and having the same receiver name) is collected from multiple Alertmanager instances then it will be deduplicated, but the UI will show all instances as source link buttons.
All merged pull requests:
0.6
release brings a major change in how alerts collected from the Alertmanager API. Previously all alerts would be de-duplicated, since Alertmanager can return same alert with multiple receivers, but with 0.6 alerts are no longer de-duplicated, instead each alert is tagged with the receiver name. New filter @receiver
allows to filter alerts based on the receiver name.
All merged pull requests:
This release support Alertmanager 0.6.2 which provides alert status details in the API so now it's possible to filter alerts based on one of the alert state values. To handle this in the unsee filters @silenced
& @inhibited
filters were removed and replaced with @state
filter. See /help
page for details.
All merged pull requests:
@status
to @state
@silenced
& @inhibited
filters with @status
Bug fixes for the silence form.
Multi-value silences created with 0.4.0
might be matching too much as they were not anchored and Alertmanager doesn't currently auto-anchor matchers (PR open), unsee will now anchor all silence regex rules.