Changelog

incident.io added as a new alert channel

You can now send SigNoz alerts to incident.io from Notification Channels.

When an alert fires in SigNoz, it can be routed to incident.io, where it can page whoever is on duty as per your on-call workflow. You don’t need the additional step of spotting an alert and forwarding it.

To set it up, use the URL and token from an HTTP alert source in incident.io. Rule labels such as severity, team, and your custom labels are sent as metadata. These can be mapped to incident.io attributes and used for routing or escalation, so you don’t need a separate notification channel for every team.

The alert notification also includes links back to the related logs and traces in SigNoz.

Billing added as a resource in custom roles

The Billing page is no longer limited to admins. You can now enable Billing permissions in a custom role and define who gets access to it.

You also have the option to configure fine-grained permissions for viewing billing information and taking billing actions. So, you can let someone see usage and invoices without letting them take any action.

Users without Billing permissions can still see the Billing page, but billing information and actions will not be available.

⚠️ Action required (API users) - migrate off the v1 alert history endpoints

The v1 alert history endpoints are deprecated and will be removed on 15 October 2026 to address a security vulnerability affecting them, tracked at #11747. Once removed, requests to the v1 endpoints will return 404 Not Found.

If you call any of the POST /api/v1/rules/{id}/history/stats, /timeline, /top_contributors or /overall_status, for example in scripts, integrations, or dashboards built on the API, move to the v2 GET /api/v2/rules/{id}/history/* equivalents. They return the same data, with some request and response schema changes (v2 uses query parameters instead of a JSON payload, cursor-based pagination, and a filterExpression string in place of the v1 filters object).

The migration guide covers the full endpoint mapping and every request/response change. Authentication and authorization are unchanged — the same API key and Viewer access continue to work.