Tempo | v2.10.4

Tempo v2.10.4 released on 13-04-2026


Tempo v2.10.4 is out now. Operators can toggle the MCP server at runtime using a new flag, so enabling MCP-related functionality no longer requires rebuilding or patching the binary.

For full details and the exact flag syntax, see the GitHub release and the implementing pull request: https://api.github.com/repos/grafana/tempo/releases/latest and https://github.com/grafana/tempo/pull/6903.

What’s in this release

  • New runtime flag to enable the MCP server (PR #6903 by @tiffanyfay).
  • Operator guidance and rollout considerations: check the flag syntax, validate the server binds to the expected port and that startup logs show success, and monitor resource and compatibility impacts.
  • Release metadata and follow-up links: published 2026-04-13 11:20:01 (Europe/London); see the release and PR for discussion and issues.

Upgrade notes

  • Review the PR/release notes for the exact flag syntax and enable the flag in a staging environment first; validate bind port and startup logs before rolling out to production.
  • If you need to revert, disable the MCP enablement flag; roll out changes gradually (canary or blue/green) and monitor for resource or compatibility issues.

Share any experience or problems on the PR discussion or by filing an issue in the Tempo repository so others can benefit from your rollout notes.

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