Tempo | v2.10.2

Tempo v2.10.2 released on 12-03-2026


Tempo v2.10.2 is out now. It restores correct exemplar behaviour end-to-end, closes a safety-cap bypass in metrics queries and centralises exemplar limits on the frontend while raising the default search max_result_limit to 256*1024.

Find the full notes and linked pull requests on the Tempo GitHub repository for implementation details and configuration options.

What’s in this release

  • Bugfix: apply exemplar hint end-to-end (ingestion through queries and visualisation) and fix safety cap bypass in metrics queries (PR #6559)
  • Enhancement: use frontend MaxExemplars config as the single source of truth for exemplar limits and add a safety cap at TraceQL engine entry points (PR #6515)
  • Change: default search max_result_limit increased to 256*1024 (262,144), which may have resource implications for some deployments (PR #6525)

Upgrade notes

  • Default search max_result_limit is now 256*1024 — operators who need a different limit should override the default in their configuration (see PR #6525 for details)
  • If the adjusted exemplar limits or the higher search result default cause issues, revert to a previous Tempo version or adjust the frontend MaxExemplars and engine safety caps as appropriate

Share your experience with this release on the project GitHub or in the community channels so others can learn from your upgrade notes and observations.

Related posts

Agentic AI still needs domain judgement

Agentic AI can write the thing, but it still cannot tell you whether the thing is right. That is where domain expertise matters, because a clean config or neat bit of glue logic can still be wrong in...

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