---
title: "V2.2 | Grafana Enterprise Traces documentation"
description: "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."
---

# 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](/docs/tempo/latest/release-notes/v2-2/) 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](/docs/enterprise-traces/latest/configure/federation/). 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](https://github.com/advisories/GHSA-4374-p667-p6c8)).

### 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