Changelog
⚠️ Action required (API users): Migrate to saved view v2 APIs
Saved view V1 APIs are deprecated since v0.137.0 and will be removed in next release v0.152.0. Please migrate to v2 if you’re using these APIs directly.
If you haven't already migrated, please follow the migration document, that outlines what changed between the API versions.
New Top List panel for dashboards
Dashboards now support a Top List panel that ranks your groups by a single value and draws each as a horizontal bar, scaled to the busiest so the leaders stand out at a glance. It is built for "which are the biggest" questions — your top services by request volume, slowest endpoints, or noisiest hosts — where a full chart is more than you need.
New Geo Map panel for dashboards
Dashboards now support a Geo Map panel that plots your data on a world map: shaded countries or states, sized bubbles, or precise latitude/longitude points. It is built for location-shaped signals like traffic, latency, or errors by region, so you can see where activity concentrates and which places are struggling at a glance.
Consistent related links in alert notifications
Related logs and traces links are now consistent across each channel's template, so Slack, Microsoft Teams, incident.io, JSM Ops, and Telegram notifications all show the same View Related Logs and View Related Traces links.
Channels on the default template update automatically on upgrade, and any related-links section you've customized is left untouched.
If you maintain your own channel or rule-body template, add the links with a single block: {{ template "signoz.relatedLinks.slack" . }} for Slack and Microsoft Teams, .markdown for incident.io and JSM Ops, and .html for Telegram.
Users added as a resource in custom roles

Managing users is no longer admin-only. We've added Users as a resource in custom roles, so you can delegate who can view, invite, edit, and delete users, and who can change their roles, without granting full admin access.
Go to Custom Roles and configure permissions for users and for the invite and password reset links. You can scope access to specific users, and scope role assignment to specific roles.
For example, you can create a role that lets a team lead promote viewers to editors and demote them back, while signoz-admin stays out of reach.
To configure users as a resource, visit Workspace settings -> Roles, select a role and scroll down to the User transaction group.
Bug Fixes
- Noz's "Open in Explorer" now opens on the time range the answer was computed for, instead of whatever the Explorer's time picker currently shows.
- The Celery "Worker Online" count now reflects the workers active over the selected time range, instead of counting dropdown entries capped at 50.