0.7.0
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:
- #142 Minor README updates
- #141 Fix inverted labels
- #136 Allow unsilencing alerts from unsee UI
- #138 Add a helper to converting ajax() call errors into a string with desc…
- #137 Don't iterate a dict, just grab the key
- #139 Re-implement metrics calculation as a collector
- #140 We'll get a panic if user sets zero or negative TTL value, add a check
- #135 Fix silence payload preview
- #134 Refactor Makefile targets to make it easier to add build tool deps
- #132 Refresh interval fixes
- #133 Move tab visibility code from grid.js to unsee.js
- #131 Fix fingerprints
- #127 Redraw alert list of user switches to unsee tab
- #128 Tweak collected metrics
- #129 Speed up alert fingerprint generation
- #126 Use share icon instead of link for alert group links
- #125 Vendor package updates
- #124 Collect alerts from multiple Alertmanager instances
- #123 Silence separator
- #122 Update license file to contain full license