---
title: "V2.8 | Grafana Enterprise Traces documentation"
description: "Learn about what's new in GET 2.8."
---

# 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](/blog/2025/06/12/grafana-tempo-2.8-release-memory-improvements-new-traceql-features-and-more/) for more examples and details about these improvements.

Review the [Tempo 2.8 release notes](/docs/tempo/latest/release-notes/v2-8/) for descriptions of the most notable changes. For a complete list, refer to the [Tempo changelog](https://github.com/grafana/tempo/releases).

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](/docs/tempo/v2-8/setup/upgrade/) 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](/docs/enterprise-traces/latest/monitoring/) 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.7

- Upgraded Go to v1.25.7. Addresses [CVE-2025-61732](https://nvd.nist.gov/vuln/detail/CVE-2025-61732), [CVE-2025-68121](https://nvd.nist.gov/vuln/detail/CVE-2025-68121)

### 2.8.5

- Upgraded Go to v1.25.5. Addresses [CVE-2025-68156](https://nvd.nist.gov/vuln/detail/cve-2025-68156), [CVE-2025-61729](https://nvd.nist.gov/vuln/detail/cve-2025-61729), [CVE-2025-61727](https://nvd.nist.gov/vuln/detail/cve-2025-61727)

### 2.8.4

- Updated Go to version 1.25.3. Addresses [CVE-2025-58183](https://nvd.nist.gov/vuln/detail/cve-2025-58183), [CVE-2025-58186](https://nvd.nist.gov/vuln/detail/CVE-2025-58186), [CVE-2025-58187](https://nvd.nist.gov/vuln/detail/CVE-2025-58187), [CVE-2025-58188](https://nvd.nist.gov/vuln/detail/CVE-2025-58188), [CVE-2025-47912](https://nvd.nist.gov/vuln/detail/CVE-2025-47912), [CVE-2025-58185](https://nvd.nist.gov/vuln/detail/CVE-2025-58185), [CVE-2025-58189](https://nvd.nist.gov/vuln/detail/CVE-2025-58189), [CVE-2025-61723](https://nvd.nist.gov/vuln/detail/CVE-2025-61723), [CVE-2025-61724](https://nvd.nist.gov/vuln/detail/CVE-2025-61724), [CVE-2025-61725](https://nvd.nist.gov/vuln/detail/CVE-2025-61725)
- Updated other vendors to address [CVE-2025-47914](https://nvd.nist.gov/vuln/detail/cve-2025-47914), [CVE-2025-58181](https://nvd.nist.gov/vuln/detail/cve-2025-58181), [GHSA-2464-8j7c-4cjm](https://github.com/advisories/GHSA-2464-8j7c-4cjm)

### 2.8.3

- Updated Go to version 1.25.1. Adresses [CVE-2025-4802](https://nvd.nist.gov/vuln/detail/cve-2025-4802), [CVE-2025-8058](https://nvd.nist.gov/vuln/detail/CVE-2025-8058), [CVE-2025-47907](https://nvd.nist.gov/vuln/detail/CVE-2025-47907), [CVE-2025-47906](https://nvd.nist.gov/vuln/detail/CVE-2025-47906)

### 2.8.2

- Updated Go to version 1.24.4. Addresses [CVE-2025-22874](https://nvd.nist.gov/vuln/detail/CVE-2025-22874), [CVE-2025-4673](https://nvd.nist.gov/vuln/detail/CVE-2025-4673), [CVE-2025-0913](https://nvd.nist.gov/vuln/detail/CVE-2025-0913), and [GHSA-FV92-FJC5-JJ9H](https://www.wiz.io/vulnerability-database/cve/ghsa-fv92-fjc5-jj9h). ([PR 5323](https://github.com/grafana/tempo/pull/5323))

### 2.8.1

- Used distroless base container images for improved security. ([PR 4556](https://github.com/grafana/tempo/pull/4556))
- Updated to go 1.24.3. ([PR 5110](https://github.com/grafana/tempo/pull/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](https://github.com/grafana/enterprise-traces/pull/1856))

### 2.8.6

- Deadlock on invalid query to api/v2/search/tags (SearchTagsV2) ([PR 5607](https://github.com/grafana/tempo/pull/5607))
- Fix Tempo configuration options that were always overridden by runtime overrides. ([PR 5202](https://github.com/grafana/tempo/pull/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](https://github.com/grafana/tempo/pull/5346))
- Return 400 Bad Request instead of 500 when an invalid tag name is provided to the SearchTagValuesV2 endpoint. ([PR 5493](https://github.com/grafana/tempo/pull/5493))
- Fix panic in query\_range http handling that could be triggered by cancellations or other errors ([PR 5667](https://github.com/grafana/tempo/pull/5667))

### 2.8.2

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

### 2.8.1

- Fixed an ingester issue where a hash collision could lead to spans stored incorrectly. ([PR 5276](https://github.com/grafana/tempo/pull/5276))
- Add metrics endpoints and combiners to federation frontend to enable TraceQL metrics and Drilldown Traces for multi-tenant and multi-cluster deployments.