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.

• 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 Tool

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:
  1. Follow the specific upgrade guide.
  2. Wait until all background migrations are finished.
  3. 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:

1. Migrate to v0.9, wait until it completes.
2. Then upgrade to v0.10.

Last updated: July 14, 2025