Upgrade SigNoz to v0.137.0 and Repair Saved Views Data

SigNoz v0.137.0 moves saved views (the named filter-and-column presets in the Logs and Traces explorers) to a typed schema. Existing views are converted automatically, so no action is needed if you use saved views only through the UI. This release also adds a Saved Views v2 API and deprecates the v1 endpoints.

The repair migration rewrites a saved view whose stored spec has unreadable fields, resetting each bad field to its empty default. A view that still cannot be parsed field-by-field is deleted from the database, and this deletion is not reversible. Back up the Metastore (SQLite or Postgres) before you upgrade. If a view is missing afterward, search the server logs for saved view data could not be repaired to find the affected saved-view IDs, then restore them from your backup.

/api/v1/explorer/views keeps working in v0.137.0, but it is deprecated and will be removed in a future release once the SigNoz UI moves to the v2 endpoints. If you call it from scripts, plan your move to the v2 API.

If you use saved views only through the UI, back up the Metastore, upgrade, then check your views for any that went missing. If you call the v1 endpoints from scripts, note that queries are now validated.

Upgrade self-hosted SigNoz

Step 1: Back up your data

Saved views live in the SigNoz Metastore alongside dashboards and alerts. Back up the Metastore before you start. If you are more than one release behind, check the Upgrade Path Tool for required stops before you move to v0.137.0.

Step 2: Upgrade SigNoz

The saved-view migrations run once, automatically, when the server starts on the new version.

Upgrade foundryctl to pick up the v0.137.0 defaults, then re-apply your existing casting.yaml:

curl -fsSL https://signoz.io/foundry.sh | bash
foundryctl cast -f casting.yaml

If your casting.yaml pins image versions, the new defaults will not override them (your config wins), so bump the SigNoz image pin to v0.137.0 yourself.

Update the chart and upgrade. Replace <namespace> and <release-name> with your own values:

helm repo update
helm -n <namespace> upgrade <release-name> signoz/signoz

helm upgrade takes the newest chart; add --version 0.137.0 to pin the v0.137.0 chart.

For Docker or binary deployments, follow the standard upgrade guide and set the target version to v0.137.0.

Step 3: Verify the upgrade

Pods and containers are healthy (kubectl get pods -n <namespace>, docker compose ps, or systemctl status 'signoz-*').
SigNoz reports v0.137.0 under Settings.
Open the Logs and Traces explorers, and confirm your saved views load and apply their filters and columns.
Search the server logs for saved view data could not be repaired. Restore any listed view from your backup.

What changes for v1 API callers

The v1 endpoints (/api/v1/explorer/views) are deprecated in v0.137.0. They keep working for now and will be removed in a future release once the SigNoz UI moves to the v2 endpoints, so plan your migration to the v2 API. Two behaviors also change behind them:

Queries are validated on create and update. A request whose query is not in the v5 query-builder format, or is otherwise invalid, is rejected with 400 Bad Request. Requests that SigNoz accepted silently before can now fail.
Unknown extraData keys are dropped. The migration and the v1 endpoints keep only the column selection (selectColumns) and the display settings (maxLines, fontSize, format, color). Anything else stored in extraData is discarded, and a malformed extraData leaves those fields empty instead of failing the request.

The new Saved Views v2 API

v0.137.0 adds /api/v2/saved_views and /api/v2/saved_views/{id}. These endpoints are new in this release, so no existing script depends on them. Migrate when you are ready.

Responses keep the standard SigNoz envelope, with the view under the top-level data field. schemaVersion and spec sit beside id and name on it, so the view spec is at response.data.spec. On requests, spec.requestType is required, and it accepts raw, raw_stream, trace, time_series, or scalar.

For the full request and response schema, see the Saved Views endpoints in the SigNoz API reference.