Menu

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.

Enterprise

Version 2.13 release notes

Grafana Labs is excited to announce the release of Grafana Enterprise Metrics (GEM) 2.13, which is built on top of Grafana Mimir 2.13.

GEM 2.13 inherits all the features, enhancements, and bug fixes that are in the Grafana Mimir 2.13 release. Given this, it’s best to start with the Grafana Mimir 2.13 release notes.

Features and enhancements

GEM has implemented enhanced usage statistics for more accurate reporting.

GEM has followed suit with Mimir 2.13 by limiting Go’s GOMAXPROCS setting to be no more than NumCPU to reduce scheduler overhead.

The grafana/enterprise-metrics docker image is now based on gcr.io/distroless/static-debian12 image. The Alpine-based docker image is still available as grafana/enterprise-metrics-alpine.

Upgrade considerations

With Grafana Mimir 2.13, mimir-continuous-test is no longer a standalone binary and is now part of Mimir as its own target. The published Docker image has been updated to use the new packaging.

The configuration option -log.buffered, deprecated in Grafana Mimir 2.11, has now been removed from Mimir 2.13. Logs are now always written in a buffered fashion.

Bug fixes

v2.13.3

  • Update build Docker image to use Go 1.22.10.
  • Upgrade to github.com/golang-jwt/jwt/v4 v4.5.1 to resolve CVE-2024-51744.
  • Upgrade to github.com/gorilla/schema v1.4.1 to resolve CVE-2024-37298.
  • Upgrade to github.com/go-jose/go-jose/v3 v3.0.3 to resolve CVE-2024-28180.
  • Upgrade to github.com/docker/cli v27.3.1 to resolve CVE-2024-41110.

v2.13.2

  • Updated base image for grafana/enterprise-metrics-alpine image to alpine:3.20.3.

v2.13.1

  • Cross-cluster query federation: fix issue where time range for label names and label values requests was not propagated to remote targets.
  • Cross-cluster query federation: log failed requests to remote targets.
  • Active series: the default value for active series idle timeout (-ingester.active-series-metrics-idle-timeout) increased from 10m to 20m.
  • Active series: active series metrics must now be enabled and their update interval must be set to 20m; otherwise, GEM fails to start.