Skip to content

Commit

Permalink
Update release notes for v2.12 (#8617) (#8620)
Browse files Browse the repository at this point in the history
This commit updates the release notes for v2.12 to include a missing
experimental feature that adds support for UTF-8 in Alertmanager,
released in Mimir v2.12.

(cherry picked from commit f61590f)

Co-authored-by: George Robinson <[email protected]>
  • Loading branch information
grafanabot and grobinson-grafana authored Jul 4, 2024
1 parent bd8bde4 commit d3536fa
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions docs/sources/mimir/release-notes/v2.12.md
Original file line number Diff line number Diff line change
Expand Up @@ -168,6 +168,11 @@ Use them with caution and report any issues you encounter:
These counts are more reactive to ring and shard changes than in-memory series, and can be used when enforcing tenant series limits by enabling the `-ingester.use-ingester-owned-series-for-limits` CLI flag.
This feature requires [zone-aware replication](https://grafana.com/docs/mimir/latest/configure/configure-zone-aware-replication/) to be enabled, and the replication factor to be equal to the number of zones.

- **Support for UTF-8 in Alertmanager** can be enabled via the `-alertmanager.utf8-strict-mode-enabled` CLI flag.
When enabled, Alertmanager can receive alerts with labels containing UTF-8 characters,
and match these alerts in routes, inhibition rules, and silences. This feature has backwards-incompatible changes.
Follow the instructions [here](https://grafana.com/docs/mimir/v2.12.x/references/architecture/components/alertmanager/#enable-utf8) to enable it.

## Bug fixes

- Distributor: fixed an issue where `-distributor.metric-relabeling-enabled` could cause distributors to panic.
Expand Down

0 comments on commit d3536fa

Please sign in to comment.