Changelog

⚠️ Action required (OSS users): Plan for extra capacity before upgrading

Log bodies are moving to native JSON storage (body_v2), which makes every field in a log body queryable by path and runs log queries faster over far less scanned data. During the transition the collector writes each log body twice, to the existing body column and the new JSON column, so dashboards, alerts, and saved views keep working unchanged.

The migration guide has a query to estimate the disk increase. Details about this change are being tracked at SigNoz/signoz#13376.

⚠️ Action required (API users): Migrate alert rules from the v1 schema to v2alpha1

The v1 alert rule schema and the /api/v1/rules endpoints will be removed on 11 November 2026. The deprecated GET /api/v2/rules list will be removed in the same release. Rules already stored in v1 are rewritten to v2alpha1 automatically when SigNoz starts after the upgrade.

Who needs to act:

• Scripts using the old endpoints: anything calling /api/v1/rules, /api/v1/testRule, or GET /api/v2/rules needs to switch to the replacement endpoints.
• Scripts using the v2 endpoints: create, replace and test requests must include "schemaVersion": "v2alpha1".
• Anything that reads rules: rules will come back in the v2alpha1 shape.
• Terraform users: no action is needed on signoz_rule; move off the older signoz_alert resource.

For UI-only users, no action is needed.

Check out the complete migration guide.

Scope roles by service and deployment environment

A role's telemetry selector can now grant access scoped to specific services (service.name) or environments (deployment.environment.name), not just a workspace key.

Give each team access to only the services it owns, or keep a role limited to staging while production data remains accessible only by administrators.

New scatter plot panel for dashboards

You can now use scatter plot dashboard panels to plot one metric against another with each point a series, like a service, route, region, or device, so correlations and outliers across many entities stand out at a glance.

Color points by a dimension, size them by a third metric for volume, and draw threshold lines to mark SLOs (for example, p95 latency vs error rate by country, or page load vs traffic by device).