Release notes on Grafana Labs

V2.8

Wed, 26 Aug 2026 20:58:36 +0000

Version 2.8 release notes

Grafana Enterprise Traces (GET) 2.8 uses Tempo 2.8 as its foundation, so it inherits all the features, enhancements, and bug fixes of the upstream project.

Read the Tempo 2.8 blog post for more examples and details about these improvements.

Review the Tempo 2.8 release notes for descriptions of the most notable changes. For a complete list, refer to the Tempo changelog.

GET is fully compatible with Tempo. You can use a GET 2.8 binary in a Tempo 2.8 deployment with minimal changes.

Note
This release has some major upgrade considerations including changing the default http-listen-port from 80 to 3200, removing serverless, and enforcing max attribute size at event, link, and instrumentation scopes.

Refer to Upgrade considerations in the Tempo documentation for details.

Features and enhancements

This release includes the following features and enhancements:

You can configure your spans via standard OpenTelemetry environment variables. For Jaeger exporting, set OTEL_TRACES_EXPORTER=jaeger. This release removes the use_otel_tracer option. For more information, refer to the OpenTelemetry documentation.

In addition, you can now configure metamonitoring to use the K8s-monitoring Helm chart. This change simplifies setting up and configuring metamonitoring for GET. Refer to Grafana Enterprise Traces metamonitoring documentation for more information.

Security fixes

The following updates were made in Tempo to address security issues. They are included in GET 2.8.

2.8.11

Upgrade Go to v1.26.6. Addresses CVE-2026-33818, CVE-2026-39821, CVE-2026-39822, CVE-2026-42505, CVE-2026-46600, CVE-2026-56853, CVE-2026-56858, CVE-2026-56859, CVE-2026-56860, CVE-2026-56862
Upgraded google.golang.org/grpc to v1.82.1. Addresses GHSA-hrxh-6v49-42gf
Upgraded golang.org/x/net to v0.58.0. Addresses CVE-2026-46600
Upgraded golang.org/x/text to v0.41.0. Addresses CVE-2026-56852
Upgraded golang.org/x/mod to v0.40.0. Addresses CVE-2026-56864, CVE-2026-56865
Upgraded go.etcd.io/etcd to v3.6.14. Addresses CVE-2026-73500
Upgraded github.com/klauspost/compress to v1.18.7. Addresses GHSA-259r-337f-4rfw

2.8.10

Upgraded golang.org/x/crypto to v0.52.0. Addresses CVE-2026-46595, CVE-2026-42508, CVE-2026-39834, CVE-2026-39833, CVE-2026-39832, CVE-2026-39831, CVE-2026-39830, CVE-2026-39829, CVE-2026-39828, CVE-2026-39827, CVE-2026-46598, CVE-2026-46597, CVE-2026-39835
Upgrade Go to v1.26.4. Addresses CVE-2026-42504, CVE-2026-27145, CVE-2026-42507, CVE-2026-33814, CVE-2026-42501, CVE-2026-39836, CVE-2026-33811, CVE-2026-42499, CVE-2026-39820, CVE-2026-39823, CVE-2026-39826, CVE-2026-39817, CVE-2026-39825, CVE-2026-39819
Upgrade github.com/apache/thrift to v0.23.0. Addresses CVE-2026-41602
Upgrade github.com/prometheus/prometheus to v0.311.3. Addresses CVE-2026-42151, CVE-2026-42154, CVE-2026-44903, CVE-2026-40179

2.8.9

Upgraded go.opentelemetry.io/otel/sdk to v1.43.0. Addresses CVE-2026-24051, CVE-2026-39883

2.8.7

Upgraded Go to v1.25.7. Addresses CVE-2025-61732, CVE-2025-68121

2.8.1

Used distroless base container images for improved security. (PR 4556)
Updated to go 1.24.3. (PR 5110)

Bug fixes

The following updates were made in Tempo to address bugs. Links to pull requests point to the original work in the Tempo 2.8 release. They are included in GET 2.8.

2.8.7

Add /api/v2/search/tags endpoint support to GET gateway and federation frontend. Fixes 404s and “Unable to fetch TraceQL tags” errors in Grafana v12.3.x. (PR 1856)

2.8.6

Deadlock on invalid query to api/v2/search/tags (SearchTagsV2) (PR 5607)
Fix Tempo configuration options that were always overridden by runtime overrides. (PR 5202)
Fix trace idle period in ingesters to be correctly applied. Add max live trace period to limit how long traces remain in memory. (PR 5346)
Return 400 Bad Request instead of 500 when an invalid tag name is provided to the SearchTagValuesV2 endpoint. (PR 5493)
Fix panic in query_range http handling that could be triggered by cancellations or other errors (PR 5667)

2.8.2

Added a nil check to partitionAssignmentVar. (PR 5198)
Corrected instant query calculation. (PR 5252)
Fixed tracing context propagation in distributor HTTP write requests. (PR 5312)
Fixed search by trace:id with short trace ID. (PR 5331]
Fixed bug where most_recent=true wouldn’t return most recent results when query overlapped ingesters and few other blocks. (PR 5438)
Fixed a panic when the counter series was missing during avg_over_time aggregation. (PR 5300)

2.8.1

Fixed an ingester issue where a hash collision could lead to spans stored incorrectly. (PR 5276)
Add metrics endpoints and combiners to federation frontend to enable TraceQL metrics and Drilldown Traces for multi-tenant and multi-cluster deployments.

V2.7

Thu, 24 Jul 2025 15:08:34 +0000

Version 2.7 release notes

Grafana Enterprise Traces (GET) 2.7.0 uses Tempo 2.7.0 as its foundation, so it inherits all the features, enhancements, and bug fixes of the upstream project.

Read the Tempo 2.7 blog post for more examples and details about these improvements.

Review the Tempo 2.7 release notes for descriptions of the most notable changes. For a complete list, refer to the Tempo changelog.

GET is fully compatible with Tempo. You can use a GET 2.7 binary in a Tempo 2.7 deployment with minimal changes.

Note
This release disables gRPC compression by default to improve performance. This change will increase data usage and network traffic, which can impact cloud billing depending on your configuration. Refer to gRPC compression for more information.

Features and enhancements

–>

Updates

Version 2.7.2 incorporates the following change from Tempo:

Default to snappy compression for all gRPC communications internal to Tempo and GET to balance of resource usage and network traffic. For a discussion on alternatives, refer to this discussion thread. (#4696)

Bug fixes

2.7.2

Fix rare panic that occurred when a querier modified results from ingesters and generators while they were being marshalled to proto. This bug also impacted query correctness on recent trace data by returning incomplete results before they were ready. (#4790)
Fix to assert READ scope instead of ADMIN on the following APIs: /api/v2/traces, /api/v2/search/tags, /api/metrics, /api/metrics/summary, /api/metrics/query, and /api/metrics/query_range.

V2.6

Thu, 24 Jul 2025 15:08:34 +0000

Version 2.6 release notes

Grafana Enterprise Traces (GET) 2.6.1 uses Tempo 2.6.1 as its foundation, so it inherits all the features, enhancements, and bug fixes of the upstream project.

Read the Tempo 2.6 blog post for more examples and details about these improvements.

Review the Tempo 2.6 release notes for descriptions of the most notable changes. For a complete list, refer to the Tempo changelog.

GET is fully compatible with Tempo. You can use a GET 2.6 binary in a Tempo 2.6 deployment with minimal changes.

V2.5

Thu, 24 Jul 2025 15:08:34 +0000

Version 2.5 release notes

Grafana Enterprise Traces (GET) 2.5 uses Tempo 2.5 as its foundation, so it inherits all the features, enhancements, and bug fixes of the upstream project.

Read the Tempo 2.5 blog post for more examples and details.

Review the Tempo 2.5 release notes for descriptions of the most notable changes. For a complete list, refer to the Tempo changelog.

GET is fully compatible with Tempo. You can use a GET 2.5 binary in a Tempo 2.5 deployment with minimal changes.

Features and enhancements

Version 2.5 adds the following enhancements.

Fixed the usage of an unknown token to return 401 Unauthorized instead of a 500 internal server error.
Fixed a panic when using the Admin API in leader elect mode.
Enhanced GET usage statistics for more accurate reporting.

V2.4

Thu, 24 Jul 2025 15:08:34 +0000

Version 2.4 release notes

Grafana Enterprise Traces (GET) 2.4 uses Tempo 2.4 as its foundation, so it inherits all the features, enhancements, and bug fixes of the upstream project.

As a result, you should read the Tempo 2.4 release notes for a description of the most notable changes.

GET is fully compatible with Tempo. You can use a GET 2.4 binary in a Tempo 2.4 deployment with minimal changes.

Features and enhancements

Version 2.4 adds the following features.

Multi-tenant support for metrics-generator

The metrics-generator now supports multi-tenant configurations. For more information, refer to Multi-tenancy configuration.

Tracing integration with profiling endpoints

With this release, GET has a tracing integration with profiling endpoints. You can use Grafana’s ability to correlate different signals by adding the functionality to link between traces and profiles. Trace to profiles lets you link your Grafana Pyroscope data source to tracing data. When configured, this connection lets you run queries from a trace span into the profile data. For more information, refer to Traces to profiles.

Updated Docker images

GET ships an additional image to support BoringCrypto. You can find the image produced here: grafana/enterprise-traces-boringcrypto.

Additionally, both the standard and BoringCrypto Docker images support both amd64 and arm64 architectures.

Other updates

This section lists additional updates and bugfixes.

2.4.1

Update golang.org/x/net package to 0.24.0 to fix CVE-2023-45288.

2.4.0

Update Alpine image version to 3.19
Add CI build for ARM64 and BoringCrypto

V2.3

Thu, 24 Jul 2025 15:08:34 +0000

Version 2.3 release notes

Grafana Enterprise Traces (GET) 2.3 builds off Tempo 2.3, so it inherits all the features, enhancements, and bug fixes of the upstream project. As a result, you should read the Tempo 2.3 release notes for a description of the most notable changes.

GET is fully compatible with Tempo. You can use a GET 2.3 binary in a Tempo 2.3 deployment with minimal changes.

Features and enhancements

GET supports OpenTelemetry Protocol (OTLP) and HTTP with a breaking change in the configurations.

Previously, both OLTP and gRPC routing configuration used the distributor_ingest block. This configuration has moved to a dedicated otlp/grpc section under the distributor block.

Previous configuration:

    distributor:
    url: ...
    distributor_ingest:
    url: ...

New configuration:

    distributor:
    url: ...
    otlp/grpc:
        url: ...
    otlp/http:
        url: ...

Bug fixes

2.3.2

Version 2.3.2 has the following fixes:

Addressed CVE-2023-5363.

2.3.1

Version 2.3.1 has the following fixes:

Fixed HTTP ingestion through the gateway.

V2.2

Thu, 24 Jul 2025 15:08:34 +0000

Version 2.2 release notes

Grafana Enterprise Traces (GET) 2.2 builds off Tempo 2.2, so it inherits all the features, enhancements, and bug fixes of the upstream project. As a result, we recommend that you read the Tempo 2.2 release notes for a description of the most notable changes.

Note: Tempo 2.2 has implemented a GPRC streaming endpoint for TraceQL queries. This capability isn’t yet supported in GET.

GET is fully Tempo-compatible. You can use a GET 2.2 binary in a Tempo 2.2 deployment with minimal changes.

Features and enhancements

GET can perform cross-tenant and cross-cluster queries using the optional federation-frontend service. This release makes the following changes to this service:

Expose per-target TLS settings
Add /api/echo endpoint. This fixes an error message that the user would have seen when configuring Grafana to query GET.

Bug fixes

2.2.4

Version 2.2.4 includes the following fix:

Update Alpine image version to 3.18.

2.2.2

Version 2.2.2 includes the following fix:

Corrects a HTTP rapid reset issue vulnerability (CVE-2023-39325).

2.2.1

Version 2.2.1 includes the following fixes:

Fix to correctly set the Host header for each proxy in the federation-frontend
Fix to correctly set Authorization header user name for each tenant in the federation-frontend

V2.1

Thu, 24 Jul 2025 15:08:34 +0000

Version 2.1 release notes

Grafana Enterprise Traces (GET) 2.1 builds off Tempo 2.1, inheriting all the features, enhancements, and bug fixes of the upstream project. As a result, we recommend that you read the Tempo 2.1 release notes for a description of the most notable changes.

GET is fully Tempo-compatible, which means you can use a GET 2.1 binary in a Tempo 2.1 deployment with minimal changes.

Bug fixes

Version 2.1.0 includes the following fixes:

Fixed a bug where /status/config wasn’t routed properly which created an endless spinner in the GET plugin.

V2.0

Thu, 24 Jul 2025 15:08:34 +0000

Version 2.0 release notes

Grafana Enterprise Traces (GET) 2.0 builds off Tempo 2.0, so it inherits all the features, enhancements, and bug fixes of the upstream project. As a result, you should read the Tempo 2.0 release notes for a description of the most notable changes.

Like Tempo 2.0, GET now includes TraceQL and uses Parquet as the default trace storage format. TraceQL is a query language modeled on PromQL and LogQL that allows you to interactively extract insights from your trace data.

To understand more about why we built TraceQL and the use cases it unlocks, see our blog post.

GET is fully Tempo-compatible: you can use a GET 2.0 binary in a Tempo 2.0 deployment with no changes.

Features and enhancements

Below we highlight some of the most important features and enhancements in GET 2.0. For a complete list of changes and enhancements, refer to the GET 2.0 changelog and the Tempo 2.0 release notes.

Cross-tenant query federation

Since GET 1.0, users could issue a single query to search multiple GET clusters at once for trace, a capability known as cross-cluster query federation. With GET 2.0, we’ve added cross-tenant query federation. This capability enables users to search multiple tenants in the same cluster at once, getting back a single, combined result.

To use cross-tenant query federation, users must run the federation-frontend service, the same service required for cross-cluster query federation. This feature supports both traceID lookups as well as TraceQL queries.

Read the cross-cluster query federation documentation for more information.

Upgrade considerations

When upgrading to GET 2.0, start by reading the Tempo 2.0 upgrade guide. Be aware of these additional breaking changes:

Removed ingester and querier routes from the GET gateway’s proxied paths.
Added support for HTTP and gRPC proxying from the GET gateway to the distributor. Configure HTTP traffic in the distributor block; configure ingest traffic (gRPC) in the distributor_ingest block.

Enhancements

This section lists a summary of the enhancements in GET 2.0. In addition to these changes, refer to the Tempo 2.0 changelog.

2.0.1

Integrate SearchTagValues V2 endpoint from Tempo with authentication and authorization model for GET.
Upgrade to Go 1.19.
Route /status endpoints in the gateway to all the components. Target components are indicated with the target query parameter.

Bug fixes

Version 2.0.1 includes the following fixes:

Fixed a bug where the Admin API licenses endpoint became permanently unusable if accessed too early.
Fixed a bug where the Admin API features endpoint wasn’t reporting version number for GET.
Fixed a bug where the license API panicked if accessed before the admin storage initialization.
Fixed query path routes by correctly appending config.http_api_prefix.

Release notes for GET V1.x

Thu, 24 Jul 2025 15:08:34 +0000

Release notes for GET 1.x

This section contains release notes for Grafana Enterprise Traces version 1.x:

V1.3
Release notes for GET version 1.3
V1.2
Release notes for GET version 1.2
V1.1
Release notes for GET version 1.1
V1.0
Release notes for GET version 1.0

Release notes on Grafana Labs

V2.8

Version 2.8 release notes

Features and enhancements

Security fixes

2.8.11

2.8.10

2.8.9

2.8.7

2.8.5

2.8.4

2.8.3

2.8.2

2.8.1

Bug fixes

2.8.7

2.8.6

2.8.2

2.8.1

V2.7

Version 2.7 release notes

Features and enhancements

Updates

Bug fixes

2.7.2

V2.6

Version 2.6 release notes

V2.5

Version 2.5 release notes

Features and enhancements

V2.4

Version 2.4 release notes

Features and enhancements

Multi-tenant support for metrics-generator

Tracing integration with profiling endpoints

Updated Docker images

Other updates

2.4.1

2.4.0

V2.3

Version 2.3 release notes

Features and enhancements

Bug fixes

2.3.2

2.3.1

V2.2

Version 2.2 release notes

Features and enhancements

Bug fixes

2.2.4

2.2.2

2.2.1

V2.1

Version 2.1 release notes

Bug fixes

V2.0

Version 2.0 release notes

Features and enhancements

Cross-tenant query federation

Upgrade considerations

Enhancements

2.0.1

Bug fixes

Release notes for GET V1.x

Release notes for GET 1.x