Menu
Documentationbreadcrumb arrow Grafana Enterprise Logsbreadcrumb arrow Release notesbreadcrumb arrow V3.3
Enterprise

Version 3.3.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.3 is built off of Loki v3.3, 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.3.0, refer to the GEL Changelog.

3.3.0 Features and enhancements

  • Updated Loki dependency to v3.3.0.
  • Query acceleration with Bloom filters (experimental): The Bloom filters feature introduced in Loki 3.0 remains experimental. There has been a major shift in how Loki leverages bloom filters — pivoting from free-text search to harnessing the power of structured metadata. This change leverages the growing adoption of OpenTelemetry in observability stacks. The Bloom Compactor component has been removed and replaced by the Bloom Planner and Bloom Builder components and blooms has a new block schema (V3) which is a breaking change.
  • cost attribution: Update usage tracker labels to change the label value for overflow scenarios from unaccounted to overflow and add a new label value missing for when the tracked label name is not found on the incoming data.
  • docs: New videos and tutorials, including a Getting Started with OpenTelemetry Collector tutorial. Also there are improvements to the Query documentation, including a new Query Best Practices topic, a reorganized Query Template, and a revised LogQL Simulator topic.

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.

The Bloom Compactor component has been removed and replaced by the Bloom Planner and Bloom Builder components and blooms has a new block schema (V3) which is a breaking change.

  • BREAKING CHANGE - blooms: Introduce a new block schema (V3) (#14038).
  • BREAKING CHANGE - blooms: Index structured metadata into blooms (#14061).

This release introduces new configuration options for some of the storage backends used in admin clients. Please refer to the configuration reference for more information.

  • BREAKING CHANGE: s3 is not selected as the default backend for admin_client, you must explicitly configure it using either the -admin.client.backend CLI flag or backend config in admin_client block.
  • BREAKING CHANGE: signature_version config is removed from s3 in admin_client block, it now always uses v4 signature.
  • BREAKING CHANGE: disable_dualstack config for s3 in admin_clientis now replaced by dualstack_enabled.
  • BREAKING CHANGE: http config for azure in admin_client blocks is removed.

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.3.0 (2024-11-19)

  • Distributor drain cache to reduce List() object storage calls Issue #2862
  • Do not fail drain cache timer service on a single failure Issue #2880
  • modules: Start the license for all components reporting analytics Issue #2902