Upgrade Guides
Upgrading SigNoz ensures you gain access to the latest features, enhancements, and security fixes. This section provides a step-by-step guide to upgrading your self-hosted SigNoz setup, including best practices and essential actions for each version.
- Upgrade guides are structured by version, indicating any necessary migration steps or breaking changes.
- Refer to the upgrade path table below to see if your upgrade requires intermediate steps, especially if you are skipping multiple versions.
- Follow the linked documentation for each version in your upgrade pathway for detailed instructions.
Release Cycle
SigNoz follows a regular schedule for new releases, with additional bug fixes and security patches when necessary.
| Release Type | Frequency | Example Versions | Notes |
|---|---|---|---|
| Minor Release | Every Wednesday | v0.87.0, v0.88.0 | Includes new features, improvements, and breaking changes |
| Bug Fix / Patch | As needed (not scheduled) | v0.87.1, v0.87.2 | Released after minor releases for urgent fixes or security patches |
- Minor releases are published weekly, typically every Wednesday.
- Bug fixes and security patches are released as necessary, with no fixed schedule.
For a complete list of releases, see the SigNoz Releases page or the changelog page
Upgrade Path
When upgrading across multiple SigNoz versions, you may encounter required upgrade stops. These are particular versions you must upgrade to before continuing, mainly due to breaking changes or key database schema updates included in those releases.
- Required upgrade stops include critical schema migrations or breaking change adjustments.
- At each stop:
- Follow the specific upgrade guide.
- Wait until all background migrations are finished.
- Proceed to the next checkpoint.
- Skipping a required stop may cause an inconsistent state or upgrade failure.
Example: To upgrade from v0.8.2 to v0.10.0:
- Migrate to v0.9, wait until it completes.
- Then upgrade to v0.10.
To plan your upgrade, find your current version in the table below and note any necessary upgrade steps along your path.
| Version | Upgrade Documentation | Description |
|---|---|---|
| v0.88.x | Upgrade to v0.88 | Migrate from underscore-based to dot-based metrics ( Dot Metrics Migration) |
| v0.76.x | Upgrade to v0.76 | Consolidate multiple services into single binary/image called signoz |
| v0.70.x | Upgrade to v0.70 | Volume Migration in Docker Standalone and Docker Swarm installations |
| v0.64.x | Upgrade to v0.64 | New Schema Changes for Logs and Traces |
| v0.55.x | Upgrade to v0.55 | Schema upgrades for Logs |
| v0.51.x | Upgrade to v0.51 | Special upgrade guide for versions older than v0.49.0 |
| v0.49.x | Upgrade to v0.49 | |
| v0.45.x | Upgrade to v0.45 | Updates dashboard panel height to new format |
| v0.38.x | Upgrade to v0.38 | Updates dashboards and alerts to support dot notation in attribute names |
| v0.36.x | Upgrade to v0.36 | Adds support for dot notation in attribute names |
| v0.27.x | Upgrade to v0.27 | |
| v0.23.x | Upgrade to v0.23 | |
| v0.19.x | Upgrade to v0.19 | Requires migration script to sanitise alerts and dashboards data |
| v0.12.x | Upgrade to v0.12 | |
| v0.10.x | Upgrade to v0.10 | Breaking release requiring data migration for errors and exceptions section |
| v0.9.x | Upgrade to v0.9 | Breaking release requiring data migration scripts for past data |
| v0.8.1 | Upgrade to v0.8.1 | Dashboard migration script required |
| v0.8.0 | Upgrade to v0.8.0 | Breaking release with data migration |
Last updated: July 14, 2025
