Changelog

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

Area chart panels in dashboards

Dashboards now support a new area chart panel type. Area charts fill the space beneath each series, making them well-suited to visualizing cumulative totals or how multiple series stack up over time.

Monitor your LLM and agent workloads with AI Observability

You can now monitor your LLM and agent workloads directly in SigNoz.

• Overview: tokens, cost, latency, and errors across models, providers, and agents.
• Explorer: query AI spans by model, provider, agent, and tool, and filter by rolled-up totals such as tokens and cost.
• Attribute mapping: span attributes from different AI frameworks are normalized into the OpenTelemetry gen_ai.* keys, so one set of queries works across all of them.
• Pricing: set per-model prices and get cost attached to every LLM span.

⚠️ Action required if you query AI spans today

Attribute mapping moves input and output messages out of framework-specific attributes into the standard gen_ai.input.messages and gen_ai.output.messages. Because these are the largest attributes on an LLM span, the original is not kept alongside the copy.

Moved keys:

• Into gen_ai.input.messages: gen_ai.prompt, ai.prompt.messages, input.value
• Into gen_ai.output.messages: gen_ai.completion, ai.response.toolCalls, ai.response.text, output.value, final_result

If your queries, saved views, or alerts reference the old keys, switch them to the standard gen_ai.* keys. Spans already using the standard keys are unaffected. To keep the original key as well, go to AI Observability → Attribute Mapping and change the operation from move to copy.