Menu
DocumentationGrafana Enterprise LogsRelease notesV3.1
Enterprise

Version 3.1.0 release notes

Note

Note that the version of GEL now reflects the version of Loki that the GEL release is based on. Patch versions are not expected to always match, but the intent is that major/minor versions should align, making it easier to tell which Loki version is included in each GEL release.

Grafana Enterprise Logs v3.1 is built off of Loki v3.1, so it inherits all the features, enhancements, and bug fixes of the upstream project. For more information about features and fixes in this release, refer to the Loki Release Notes and the Loki CHANGELOG.

Note

Note that Loki 3.x defaults to using the v13 schema. All of the latest features are built against TSDB and the v13 Schema. This version of the schema is compatible with both Loki 2.9.x and Loki 3.x. The main change is to add support for Structured Metadata which is used by the new OTLP native endpoint and is enabled by default.

Features and enhancements

For the full list of features, enhancements and bug fixes in GEL 3.1.0, refer to the GEL Changelog.

3.1.0 Features and enhancements

  • Updated Loki dependency to v3.1.0.
  • Enhanced GEL usage statistics for more accurate reporting.
  • Explore Logs: Explore Logs, which lets you explore your Loki data without writing LogQL queries, is now available in public preview. If you are a Grafana Cloud user, you can access Explore Logs in the Grafana Cloud main navigation menu. If you are not a Grafana Cloud user, you can install the Explore Logs plugin. For more information, refer to the Explore Logs documentation.

Upgrade Considerations

The path from Loki 2.9.x to 3.0.0 includes several breaking changes. For important upgrade guidance, refer to the Upgrade Guide and the separate Helm Upgrade Guide.

  • BREAKING CHANGE Update Helm chart to support distributed mode and 3.0 (#12067).

Caution

Out of an abundance of caution, we advise that users with Loki or Grafana Enterprise Logs (GEL) deployments on AWS upgrade their Helm charts or change the names of their buckets, as outlined in the solutions and mitigations section of this blog post.

Bug Fixes

3.1.0 bug fixes