Changelog

PromQL conformance with the Prometheus specification

SigNoz's PromQL implementation had several gaps where its behavior diverged from Prometheus. This release brings it into line with the Prometheus spec.

⚠️ Action may be required: regex matchers are now anchored, matching Prometheus. env=~"foo" is now treated as env=~"^foo$". Previously SigNoz did substring matching, so a pattern could over-match — job=~"api" also matched api-server. If you relied on substring behavior, wrap the pattern explicitly: use =~".*foo.*" for contains, =~"foo.*" for prefix, and write glob-style habits like name* as name.*. This is the one change that can alter the results of existing queries.

Also fixed, all bringing the PromQL implementation in line with Prometheus semantics:

• Selectors without an exact metric name now work — nameless selectors ({job="api"}), regex metric names ({__name__=~"prod_.+"}), and negations previously returned empty results silently.
• Series identity now follows Prometheus semantics, so without() aggregations no longer return duplicate series and vector matching joins correctly.
• Series first seen exactly at a query window's end are no longer missed.
• User labels beginning with __ (e.g. __address__) are preserved; only SigNoz-internal storage keys are stripped.

Investigate and optimize telemetry costs with Noz or your AI agent

You can now investigate telemetry costs using Noz in SigNoz Cloud or the telemetry cost investigation skill from any AI agent.

Ask “Why is my bill high?” or “Help me optimize costs.” The skill analyzes Cost Meter data, ranks telemetry by ingestion volume, checks whether the data is used in dashboards or alerts before recommending what to drop, and identifies further optimization opportunities.

In SigNoz Cloud, you can run the investigation directly from Noz. Cloud and Community Edition users can also invoke the same skill using a SigNoz plugin or an individual agent skill.

When an AI agent has access to your codebase, it can apply the recommended instrumentation and configuration changes directly.

Table export in the Logs and Traces explorers

You can now export results from the table tabs in the Logs and Traces explorers as CSV or JSONL, bringing them to parity with the other explorer views.

PromQL conformance with the Prometheus specification

SigNoz's PromQL implementation had several gaps where its behavior diverged from Prometheus. This release brings it into line with the Prometheus spec.

⚠️ Action may be required: regex matchers are now anchored, matching Prometheus. env=~"foo" is now treated as env=~"^foo$". Previously SigNoz did substring matching, so a pattern could over-match — job=~"api" also matched api-server. If you relied on substring behavior, wrap the pattern explicitly: use =~".*foo.*" for contains, =~"foo.*" for prefix, and write glob-style habits like name* as name.*. This is the one change that can alter the results of existing queries.

Also fixed, all bringing the PromQL implementation in line with Prometheus semantics:

• Selectors without an exact metric name now work — nameless selectors ({job="api"}), regex metric names ({__name__=~"prod_.+"}), and negations previously returned empty results silently.
• Series identity now follows Prometheus semantics, so without() aggregations no longer return duplicate series and vector matching joins correctly.
• Series first seen exactly at a query window's end are no longer missed.
• User labels beginning with __ (e.g. __address__) are preserved; only SigNoz-internal storage keys are stripped.

Investigate and optimize telemetry costs with Noz or your AI agent

You can now investigate telemetry costs using Noz in SigNoz Cloud or the telemetry cost investigation skill from any AI agent.

Ask “Why is my bill high?” or “Help me optimize costs.” The skill analyzes Cost Meter data, ranks telemetry by ingestion volume, checks whether the data is used in dashboards or alerts before recommending what to drop, and identifies further optimization opportunities.

In SigNoz Cloud, you can run the investigation directly from Noz. Cloud and Community Edition users can also invoke the same skill using a SigNoz plugin or an individual agent skill.

When an AI agent has access to your codebase, it can apply the recommended instrumentation and configuration changes directly.

Table export in the Logs and Traces explorers

You can now export results from the table tabs in the Logs and Traces explorers as CSV or JSONL, bringing them to parity with the other explorer views.

Data export: timeseries from all explorers, download in the Trace View

You can now export timeseries data from the Time Series view across all explorers, making it easier to pull query output into your own analysis, reporting, or archival workflows.

Additionally, the Trace View in the Traces explorer now also supports download, as CSV or JSONL

More Onboarding Integrations

You can now onboard six additional data sources directly from SigNoz: NGINX Ingress, FluxCD, Cassandra, Cloudflare Workers, PlanetScale, and the Hermes Agent. Each data source comes with a guided setup so you can start collecting telemetry without hand-rolling the configuration.

Infrastructure Monitoring: streamlined Kubernetes navigation and Host disk usage

Navigating between Kubernetes resource types in Infrastructure Monitoring is now quicker and cleaner, with a reworked category selection that makes it easier to move between hosts, pods, and other resources.

You can now also track disk usage by mount point for each Host resource.

Fine-grained access control (beta)

Fine-grained access control is now available in beta for all Cloud and Self-Hosted Enterprise users. Previously, only admins could manage service accounts, their API keys, and roles, which made it an all-or-nothing model. You can now create custom roles with scoped permissions and delegate those responsibilities to the right people without granting full admin access.

Create a custom role that can manage service accounts, API keys, and roles, then assign it to a user instead of making them an admin, or scope a role down to control exactly who can create, edit, or delete roles. You'll find everything under Settings → Identity & Access. See the Roles guide to get started.

Note: assigning roles to users remains admin-only for now. As this feature is in beta, we'd love your bug reports and feedback.

Self-service API keys for viewers

Building on fine-grained roles, admins can now set up a self-service flow so viewer users generate their own read-only API keys without routing every request through an admin, and without granting broad permissions. This is especially useful for giving read-only users direct access to the SigNoz MCP Server for AI tooling.

The setup is a one-time admin task: create a read-only service account, build a custom role scoped to add keys to just that account, and assign it to viewers by invite or SSO. The step-by-step guide walks through it.

⚠️ Upgrade to ClickHouse 25.12.5 to stay on supported releases

Upcoming versions of SigNoz will begin leveraging features, such as storing trace attributes as JSON, provided by newer versions of ClickHouse. In future releases, the bundled signoz-otel-collector will require ClickHouse 25.12.5 or greater.

We recommend you plan for an upgrade to ClickHouse 25.12.5, before a future SigNoz makes it mandatory and drops support for older versions. Please ensure you back up your data and follow along this guide to ensure a seamless upgrade.

Noz: SigNoz's AI Teammate, Now Available to All Cloud Users

Noz is SigNoz's built-in AI teammate, and it's now available to all Cloud users. When you ask about your telemetry, alerts, dashboards, and other configuration in plain English, Noz investigates across the platform to answer your questions based on live data.

You can open Noz as a side panel alongside your current view from the top right corner of any SigNoz page. Once it has answered your query, it suggests follow-up actions, such as saving the current view, setting up an alert, or creating a dashboard.

Azure Database Services Support

You can now monitor Azure Database services out of the box, including Azure SQL Database, Azure Cosmos DB, Azure Database for PostgreSQL, and Azure Database for MySQL. Combined with the VM, App Services, Container Apps, and AKS support added in v0.128.0, Azure-heavy teams can now observe a much broader slice of their infrastructure without additional setup.

Recent Queries in the Query Builder

The query builder now surfaces your recent queries across Logs Explorer, Metrics Explorer, Traces Explorer, the Alert Builder, and the Dashboard Panel Editor. You can now keep track of and re-run previous investigations without manually typing them out.

The queries are grouped per signal type and appear inline, simplifying access path to the queries you run regularly.

Azure monitoring: VMs, App Services, Container Apps, and AKS

You can now monitor a much broader set of Azure resources in SigNoz. This release adds support for Azure VMs, plus out-of-the-box assets and dashboards for Azure App Services, Azure Container Apps, and Azure AKS, so that common Azure workloads are observable without manual dashboard setup.

Paginated, clickable Alerts and Triggered Alerts

The Alerts list and Triggered Alerts views have been rebuilt on a new table. Triggered Alerts is now paginated implying no more loading everything at once with the current page preserved in the URL so it survives refreshes and is easy to share. Triggered alerts are now clickable and link straight back to the rule that fired them, so you can go from "what fired" to "why" in a single click. Empty and error states across both pages are also more consistent now.