Version 2.5 release notes
Grafana Labs is excited to announce the release of Grafana Enterprise Metrics (GEM) 2.5, which is built on top of Grafana Mimir 2.5.
GEM 2.5 inherits all of the features, enhancements, and bugfixes that are in the Grafana Mimir 2.5 release. Given this, it’s best to start with the Grafana Mimir 2.5 release notes.
Features and enhancements
TLS is now more configurable for both internal and external connections
-*.tls-min-versionto configure the minimum TLS version
-*.tls-cipher-suitesto allow overriding the default cipher suites provided by the Go runtime
GEM Self Monitoring cpu metrics now include a
clusternamelabel to distinguish multiple installations of Grafana Enterprise Metrics, Grafana Enterprise Logs and Grafana Enterprise Traces.
GEM Self Monitoring bundles 16 additional recording rules from the Grafana Mimir monitoring mixin.
The object storage parameters
-*.azure.msi-resourceare now ignored, and will be removed in GEM 2.7. This setting is now chosen automatically by Azure.
The Graphite Querier’s default cache TTL has been lowered to 10 minutes. This ensures consistent query results when out-of-order ingestion is enabled.
The storage aggregation method set for the Graphite Querier in
storage-aggregation.confcan no longer be overridden during runtime using
consolidateBywhen metrictank is used as a render engine. This matches Graphite-Web’s behavior.
Fixed a bug in the Graphite Querier where render requests that failed to be processed by the native engine were not being proxied to Graphite-Web.
The mimir-distributed Helm chart is the best way to install GEM on Kubernetes. Notable changes follow. For the full list of changes, see the Helm chart changelog.
Zone aware replication Helm now supports deploying the ingesters and store-gateways as different availability zones. The replication is also zone-aware, therefore multiple instances of one zone can fail without any service interruption and roll outs can be performed faster because many instances of each zone can be restarted together, as opposed to them all restarting in sequence.
This is a breaking change, for details on how to upgrade please review the Helm changelog.
This release also inherits the helm changes from the Grafana Mimir 2.5 release.
- There are no breaking changes in this release of GEM
- If you are deploying via Helm, note the Helm changes above.
This release also inherits the upgrade considerations from the Grafana Mimir 2.5 release.
After you upgrade to GEM 2.5, upgrade your GEM plugin to the latest version. For more information about the most recent enhancements and bugfixes in the GEM plugin, see the Grafana Enterprise Metrics: Changelog.
- Fixed empty buildinfo in GEM binary