This is documentation for the next version of Grafana Tempo documentation. For the latest stable release, go to the latest version.
Recommended versions
Grafana Tempo follows a regular release cadence. Knowing which versions Grafana recommends helps you plan upgrades and make sure you receive bug fixes and security patches.
This page applies to self-managed Tempo installations. Grafana Cloud follows a different release process.
Release types
Tempo releases use semantic-like versioning (MAJOR.MINOR.PATCH):
- Major release (roughly once a year): May include new architecture, significant features, and breaking changes that require migration steps.
- Minor release (roughly every three to four months): Includes new features and enhancements. May occasionally include minor breaking changes documented in the upgrade guide.
- Patch release (as needed): Includes bug fixes and security patches only. No new features.
Version recommendation policy
These timelines are guidance; always consult the release notes for the most up-to-date information. For self-managed Tempo, version recommendations follow these rules:
- Each minor release receives bug fixes and security patches for 9 months after its release date.
- The last minor release of a major version receives bug fixes and security patches for 15 months after its release date.
Recommendation levels change as new versions are released:
High severity security vulnerabilities and critical feature degradation incidents may result in ad-hoc patch releases outside the normal schedule.
Current versions
Here is an overview of version status:
Warning
Tempo 2.8 has reached end of life (EOL) and no longer receives bug fixes or security patches. If you’re running Tempo 2.8, upgrade to a recommended version.
Upgrade strategies
Based on your needs, choose an upgrade cadence:
For the best experience, follow the minor release cadence. You can occasionally extend to a full quarter and still receive security fixes for your currently deployed version.
Before upgrading, always read the upgrade guide for your target version.
Minimize upgrade risk
- Test first: Test upgrades in a non-production environment before deploying to production.
- Back up: Back up your configuration and data before upgrading.
- Stay current: Running a recommended version means you receive security patches and bug fixes.
- Read the changelog: Review the release notes and upgrade guide before upgrading.

