|
1 |
| -## Next release |
2 |
| - |
3 |
| -This release includes changes to amtool which are not fully backwards compatible with the previous |
4 |
| -amtool version (#1798) related to backup and import of silences. If a backup of silences is created using |
5 |
| -a previous version of amtool (v0.16.1 or earlier), it is possible that not all silences can be correctly imported using a later version of amtool. |
6 |
| - |
| 1 | +## 0.17.0 / 2019-05-02 |
| 2 | + |
| 3 | +This release includes changes to amtool which are not fully backwards |
| 4 | +compatible with the previous amtool version (#1798) related to backup and |
| 5 | +import of silences. If a backup of silences is created using a previous |
| 6 | +version of amtool (v0.16.1 or earlier), it is possible that not all silences |
| 7 | +can be correctly imported using a later version of amtool. |
| 8 | + |
| 9 | +Additionally, the groups endpoint that was dropped from api v1 has been added |
| 10 | +to api v2. The default for viewing alerts in the UI now consumes from this |
| 11 | +endpoint and displays alerts grouped according to the groups defined in the |
| 12 | +running configuration. Custom grouping is still supported. |
| 13 | + |
| 14 | +This release has added two new flags that may need to be tweaked. For people |
| 15 | +running with a lot of concurrent requests, consider increasing the value of |
| 16 | +`--web.get-concurrency`. An increase in 503 errors indicates that the request |
| 17 | +rate is exceeding the number of currently available workers. The other new |
| 18 | +flag, --web.timeout, limits the time a request is allowed to run. The default |
| 19 | +behavior is to not use a timeout. |
| 20 | + |
| 21 | +* [CHANGE] Modify the self-inhibition prevention semantics (#1873) |
7 | 22 | * [CHANGE] Make api/v2/status.cluster.{name,peers} properties optional for Alertmanager with disabled clustering (#1728)
|
| 23 | +* [FEATURE] Add groups endpoint to v2 api (#1791) |
| 24 | +* [FEATURE] Optional timeout for HTTP requests (#1743) |
| 25 | +* [ENHANCEMENT] Set HTTP headers to prevent asset caching (#1817) |
| 26 | +* [ENHANCEMENT] API returns current silenced/inhibited state of alerts (#1733) |
| 27 | +* [ENHANCEMENT] Configurable concurrency limit for GET requests (#1743) |
| 28 | +* [ENHANCEMENT] Pushover notifier: support HTML, URL title and custom sounds (#1634) |
| 29 | +* [ENHANCEMENT] Support adding custom fields to VictorOps notifications (#1420) |
8 | 30 | * [ENHANCEMENT] Migrate amtool CLI to API v2 (#1798)
|
| 31 | +* [ENHANCEMENT][ui] Default alert list view grouped by configured alert groups (#1864) |
| 32 | +* [ENHANCEMENT][ui] Remove superfluous inhibited/silenced text, show inhibited status (#1698, #1862) |
| 33 | +* [ENHANCEMENT][ui] Silence preview now shows already-muted alerts (#1776) |
| 34 | +* [ENHANCEMENT][ui] Sort silences from api/v2 similarly to api/v1 (#1786) |
| 35 | +* [BUGFIX] Trim PagerDuty message summary to 1024 chars (#1701) |
| 36 | +* [BUGFIX] Add fix for race causing alerts to be dropped (#1843) |
| 37 | +* [BUGFIX][ui] Correctly construct filter query string for api (#1869) |
| 38 | +* [BUGFIX][ui] Do not display GroupByAll and GroupBy in marshaled config (#1665) |
| 39 | +* [BUGFIX][ui] Respect regex setting when creating silences (#1697) |
| 40 | + |
| 41 | +## 0.16.2 / 2019-04-03 |
| 42 | + |
| 43 | +Updating to v0.16.2 is recommended for all users using the Slack, Pagerduty, |
| 44 | +Hipchat, Wechat, VictorOps and Pushover notifier, as connection errors could |
| 45 | +leak secrets embedded in the notifier's URL to stdout. |
| 46 | + |
| 47 | +* [BUGFIX] Redact notifier URL from logs to not leak secrets embedded in the URL (#1822, #1825) |
| 48 | +* [BUGFIX] Allow sending of unauthenticated SMTP requests when `smtp_auth_username` is not supplied (#1739) |
9 | 49 |
|
10 | 50 | ## 0.16.1 / 2019-01-31
|
11 | 51 |
|
|
0 commit comments