Tempo v3.0.0 released on 28-05-2026
Tempo v3.0.0 is out now. Operators and platform teams should prepare for a breaking migration: the release completes the move to a new ingest/write architecture and removes legacy ingesters, v2 blocks and the legacy compactor.
Read the official release notes and the migration and upgrade guides for full instructions and tooling: https://grafana.com/docs/tempo/latest/release-notes/v3-0/, https://grafana.com/docs/tempo/latest/set-up-for-tracing/setup-tempo/migrate-to-3/, https://grafana.com/docs/tempo/latest/set-up-for-tracing/setup-tempo/upgrade/ (changelog: https://github.com/grafana/tempo/blob/v3.0.0/CHANGELOG.md#v300).
What’s in this release
- New ingest/write architecture: legacy ingesters and the ingester-based write path removed; block/WAL configuration centralised under storage.trace.block.
- TraceQL metrics graduates to general availability; vParquet5 receives performance and correctness improvements and a faster read path remains available experimentally behind query hints and per‑tenant opt‑ins.
- Breaking configuration changes and migration tooling: many config fields and modules removed or renamed, legacy overrides disabled by default, and tempo-cli gains migrate config and overrides helpers.
Upgrade notes
- This is a breaking release for operators. Review the migration and upgrade guides before upgrading and run tempo-cli migrate where appropriate; removed fields include querier.query_live_store and several compactor/block config names.
- If you rely on legacy flat overrides you can temporarily opt back in with enable_legacy_overrides: true or -config.enable-legacy-overrides=true, but the legacy ingester write path and v2 components have been removed and require following the migration guide to replace.
Share any comments or issues you encounter with the upgrade on the project’s GitHub (see the changelog/release links above) so others can learn from your experience.
