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.


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


  • 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.