Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Version 2.1 release notes
Grafana Labs is excited to announce the release of Grafana Enterprise Metrics (GEM) 2.1. GEM 2.1 is built on top of Grafana Mimir 2.1, which means it inherits all its features, enhancements, and bugfixes. Given this, we recommend you start by reading the Grafana Mimir 2.1 release notes.
Below, we highlight the most important features, enhancements, and bugfixes specific to GEM 2.1. For the full list of changes, see the Changelog.
Features and enhancements
The following list highlights the features and enhancements in Grafana Enterprise Metrics 2.1:
Remoteruler mode for improved rule evaluation performance: This experimental feature is inherited from Grafana Mimir 2.1 and is explained in more detail in the Mimir 2.1 release notes. GEM 2.1 adds an additional configuration parameter,
-ruler.query-frontend.auth-token, which is required for configuring the
remoteruler with GEM enterprise authentication. See Remote rule evaluation for more information.
- Page fault metrics for self-monitoring: GEM now collects and stores metrics tracking the number of page faults and out-of-memory kills it experiences, making it easier to debug performance issues.
We’ve released a new version of our Helm chart in tandem with the GEM 2.1 release. The upgrade for users of the Helm chart has no breaking changes.
Once you upgrade to GEM 2.1, we recommend you upgrade your Grafana Enterprise GEM plugin to the latest version. For more information on the most recent enhancements and fixes, see the plugin’s changelog page.
- Fixed a bug where ruler limits (e.g., maximum number of rules in a rule group or maximum number of rule groups per tenant) were not enforced when creating a rule group via GEM’s ruler API. These limits are now enforced.
- GEM now returns a generic error message to clients (e.g., the Grafana Agent) upon internal errors during authentication. The detailed error message is now written to the GEM logs rather than being returned to the client.