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

Version 3.4.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.4 is built off of Loki v3.4, 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.4.0, refer to the GEL Changelog.

3.4.0 Features and enhancements

  • Updated Loki dependency to v3.4.0.
  • cost attribution: Update cost attribution watcher to support v1 and v2 attributionlabelname CRDs; go mod vendor && go mod tidy; update tests for single and multi-label scenarios (#3108) (b2beb9c).
  • OTel migration: Track bill free ingestion based on a specific header set by our internal proxies. To assist customers pinned to the old OTLP ingestion format in their migration from old to new OTLP format, we will perform dual ingestion of logs in both the old and new formats. However, customers will not be double billed for the migration period. (#3180) (71185b8).

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.4.0 (2025-02-14)

  • ci: Use the right branch target for publish weekly images job (backport weekly-k239) (#3242) (6e8e2fc).
  • deps: Update k8s.io/api to v0.32.1 (cb932e6).
  • deps: Update module github.com/aws/aws-sdk-go to v1.55.6 (#3183) (4bc1c1b).
  • deps: Update module github.com/grafana/e2e to v0.1.1 (#3007) (07e8e4b).
  • metrics: Add loki_ metric prefix to usage purge metrics; fix ActiveTrackersCount usage metric decrementing (#3234) (#3252) (c892314).