Changelog

AI traces are now easy to read with the new Thread View

AI workflows carry far more useful information than duration and performance. To understand what happened, you need to read the input and output messages, token usage, tool calls, and model names. A standard trace view doesn’t make that easy.

In span details, the input and output messages were packed into a single block of raw JSON. Not a pleasant place to read and inspect.

So we’ve made AI traces readable with a new conversation-based Thread view. You can now see the full chain of LLM calls laid out as a conversation, with the input and output messages, reasoning, tool calls and tool results for each step.

The span details panel also shows the input and output messages for each AI span, and you can switch between a Formatted and a JSON view.

The Thread view works with LLM data from most popular providers and frameworks, in addition to the standard OTel gen_ai.* format. That includes OpenAI, Anthropic, Gemini, OpenRouter, LangChain, Vercel AI SDK, Mastra, pydantic-ai, LiteLLM, OpenInference, and OpenLLMetry.

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

Anomaly alerts moved to the new alert experience

We’ve moved anomaly alerts to the new alert experience. Now, you create them using the new alert form, similar to threshold alerts.

The anomaly condition now reads like a sentence, with the query, direction, match type and window, then the algorithm and seasonality, then one row per severity with its deviation and channels.

What else is new in the new experience for anomaly alerts:

• The deviation is a number above 0, so values like 2.5 work.
• ON AVERAGE and LAST join the match types.
• The anomaly query function carries the deviation and seasonality, so the preview band matches what the rule checks.
• Switching between Threshold and Anomaly keeps your query.

Anomaly alerts are available on SigNoz Cloud and Enterprise self-hosted, for query builder metric queries. Your existing anomaly alerts still open in the classic form.

One-click setup for GCP integration

Now, you can connect your GCP account without setting up a collector. When adding a GCP account, choose Connect via Agent. SigNoz will deploy and manage the collector for you.

Enter your project and region, click Generate Command, and run the command in Google Cloud Shell or any terminal with gcloud set up. SigNoz then checks for the connection automatically.