Tempo | v3.0.0

Tempo v3.0.0 released on 28-05-2026


Tempo v3.0.0 is out now. Operators should pay attention: the release replaces the legacy ingester-based write path with a new ingest/write architecture, removes v2 block encoding and several deprecated flags, and graduates TraceQL metrics to GA.

Read the migration guide and upgrade instructions before changing production deployments — key references: Migration guide, Upgrade guide, and the Release notes (changelog: GitHub).

What’s in this release

  • New ingest/write architecture replacing legacy ingesters, with single-binary and distributed behaviours updated and improved live-store correctness and observability.
  • Breaking changes and cleanup: removal of v2 block encoding, deprecation of many per-module block/WAL configs now centralised under storage.trace.block, and several deprecated flags/receivers removed or disabled by default.
  • TraceQL metrics reaches GA (with an experimental faster read path behind a hint), vParquet5 improvements for performance and correctness, and expanded metrics-generator controls for cardinality.

Upgrade notes

  • Major breaking changes: the legacy ingester-based write path is removed and v2 blocks/compactor are gone — follow the migration guide and upgrade guide for step‑by‑step actions and gotchas.
  • Temporary fallback for legacy overrides: Tempo now refuses to start if legacy overrides are detected; set enable_legacy_overrides: true or use -config.enable-legacy-overrides=true to opt back in briefly, but validate in staging because a full rollback may not be straightforward.

Share comments on your upgrade or migration experience so others can learn from real-world issues and fixes.

Related posts

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...

restic | v0.19.1

restic v0 19 1: safer FUSE mounts and mountpoint checks, robust backup source and exclude handling, clearer CLI JSON output, Windows SFTP deletion fixes