Changelog

⚠️ 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.

New Saved Views across Explorers

We’ve updated Saved Views. Previously, you had to open a separate Views tab on top to find and manage your saved views.

Now, the saved views sit in the left sidebar along with the filters. You can open, save, and manage the saved views without leaving the page.

This is live across explorers - Logs, Traces, Metrics and Meter Explorers.

What’s new in Saved Views,

• Views are split into views created by you and views created by others. You can also search them by name.
• Hovering a view shows a preview of its filters and when it was last updated, even before you open it.
• From a view’s ... menu, you can copy its link to share it, edit its details or delete it.
• To close an opened view and just go back to a regular Explorer, click ↺ next to it.
• If you don’t have any saved views yet, you can create one straight from the empty panel with Create view.

New bottom strip with Support chat

SigNoz now has a new bottom strip across every page. It enables quick access to Support and Ask Noz. Support replaces the floating chat bubble. Now, you can reach our support team from the right side of the strip.

The left side of the strip shows details about the page you’re on. For example, in Trace Details it shows the number of spans and errors in the trace.

Moved Notification Channels to v2 API

We’ve redesigned the Notification Channels page and moved it onto our v2 API.

What’s new in Notification Channels,

• The channels list now matches the rest of SigNoz. Your channel search and filters are saved in the URL, so the filtered list stays after a reload and can be shared.
• When you filter the list by a channel type, such as Jira or Google Chat, you can create a new channel of that type straight from the filtered list.
• Slack channels have more options for how alert messages look, including colour, title link, pretext, footer, fields and action buttons.
• You can view a channel’s full settings as JSON. Passwords and tokens stay hidden until you choose to reveal them.

Channel dropdowns in alert rules and routing policies now load all your channels. Previously, they were capped at 200 channels.

Telegram added as a new alert channel

You can now send SigNoz alerts to Telegram from Notification Channels. When an alert fires in SigNoz, it’s posted to the Telegram chat, group or channel you’ve set up.

To set it up, add your bot token and the numeric chat ID. You can also set a forum topic ID, a message template, a self-hosted Bot API URL, and choose to send alerts silently.

If an alert rule has its own title and body templates, those replace the channel’s message, matching the other custom channels.

Telegram only supports a limited set of formatting, so headings, lists, tables and images in the alert message are converted to plain text before sending.

Logs support in GCP Integration

GCP Integration now collects logs as well as metrics, so your Google Cloud logs sit alongside your GCP metrics in SigNoz. Logs are available through the manual setup flow. Check out the GCP Integration docs to get started.

v1 alert history endpoints removed

The v1 alert history endpoints have now been removed and return 404 Not Found. If you still use them, switch to the v2 GET /api/v2/rules/{id}/history/* endpoints using the migration guide.