Changelog
⚠️ Action required (API users): Migrate to saved view v2 APIs
Saved view V1 APIs are deprecated since v0.137.0 and will be removed in next release v0.152.0. Please migrate to v2 if you’re using these APIs directly.
If you haven't already migrated, please follow the migration document, that outlines what changed between the API versions.
New Top List panel for dashboards
Dashboards now support a Top List panel that ranks your groups by a single value and draws each as a horizontal bar, scaled to the busiest so the leaders stand out at a glance. It is built for "which are the biggest" questions — your top services by request volume, slowest endpoints, or noisiest hosts — where a full chart is more than you need.
New Geo Map panel for dashboards
Dashboards now support a Geo Map panel that plots your data on a world map: shaded countries or states, sized bubbles, or precise latitude/longitude points. It is built for location-shaped signals like traffic, latency, or errors by region, so you can see where activity concentrates and which places are struggling at a glance.
Consistent related links in alert notifications
Related logs and traces links are now consistent across each channel's template, so Slack, Microsoft Teams, incident.io, JSM Ops, and Telegram notifications all show the same View Related Logs and View Related Traces links.
Channels on the default template update automatically on upgrade, and any related-links section you've customized is left untouched.
If you maintain your own channel or rule-body template, add the links with a single block: {{ template "signoz.relatedLinks.slack" . }} for Slack and Microsoft Teams, .markdown for incident.io and JSM Ops, and .html for Telegram.
Users added as a resource in custom roles

Managing users is no longer admin-only. We've added Users as a resource in custom roles, so you can delegate who can view, invite, edit, and delete users, and who can change their roles, without granting full admin access.
Go to Custom Roles and configure permissions for users and for the invite and password reset links. You can scope access to specific users, and scope role assignment to specific roles.
For example, you can create a role that lets a team lead promote viewers to editors and demote them back, while signoz-admin stays out of reach.
To configure users as a resource, visit Workspace settings -> Roles, select a role and scroll down to the User transaction group.
Bug Fixes
- Noz's "Open in Explorer" now opens on the time range the answer was computed for, instead of whatever the Explorer's time picker currently shows.
- The Celery "Worker Online" count now reflects the workers active over the selected time range, instead of counting dropdown entries capped at 50.
⚠️ Action required (API users): v1 alert rules APIs removed
Alert rules now use a single schema, v2alpha1. From this release, the v1 rules APIs are removed. Your existing rules are converted 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, orGET /api/v2/rulesmust switch to the replacement endpoints. - Scripts using the v2 endpoints: create, replace, and test requests must include
"schemaVersion": "v2alpha1". - Anything that reads rules: rules now come back in the v2alpha1 shape.
- Terraform users: no action is needed on
signoz_rule. Move off the oldersignoz_alertresource.
For UI-only users, no action is needed.
Read the v0.150 upgrade guide before upgrading.
Alert Rules list moved to the v3 API, with new search and saved views
The Alert Rules list now uses the new /api/v3/rules API. Search, filtering and pagination now run server-side, so the browser only loads the page you’re viewing.
The search bar takes filters such as name, severity, alert type, rule type, created by, and labels, with autocomplete as you type.
We’ve also added saved views, which sit alongside the list. You can build views around your apps, your infrastructure, or any logic you want, and they are shared with your organization. You also get four built-in views: My alert rules, All, Firing, and Disabled.
Traces Explorer gets a new span drawer and infinite scroll
Reading spans in the Traces Explorer list is now easier. Clicking a row opens the span in a side drawer. You no longer have to open the trace page and come back to check the next span.
The drawer shows the same overview, events, and logs tabs as the trace page. Use the up and down buttons or the arrow keys to step through the rows. Click outside the table to close it.
The list view now loads spans as you scroll, 100 at a time, until it reaches the end of the results or the query limit. The Previous and Next buttons are gone.
Hovering a row shows an icon to open the full trace in a new tab.
Self-hosted Jira added to the Jira alert channel
You can now send SigNoz alerts to self-hosted Jira. This covers Jira Server and Data Center, version 8.14 or newer.
When creating a Jira channel, choose where your Jira runs. Self-hosted uses a personal access token. Cloud still uses your email and API token. Existing Jira Cloud channels keep working without changes.
If you manage channels through the API, the Jira spec has changed. deployment is now required, and credentials sit under auth.
Saved views and column options in AI Observability
You can now save a view in the AI Observability Explorer. Come back to it any time to monitor the same data or continue an investigation, without rebuilding it.
The list view also gets a column picker. You can choose which columns to show and arrange them the way you want. Your columns are saved with the view and carried in the URL.
Pie charts group small slices into Other
Pie charts with many groups are now easier to read. Slices under 1% of the total are grouped into a single Other slice. A pie also shows at most 15 slices.
The legend still lists every series. Hover over Other to see what’s inside it. Click it to pin the list, then click a member to drill into that series.
This happens automatically on the new dashboards, with no panel setting to change.
⚠️ Action required (OSS users): Plan for extra capacity before upgrading
Log bodies are moving to native JSON storage. From this release, logs are dual-ingested. The collector writes each log body twice: to the existing body column and to the new JSON column. Your dashboards, alerts, and saved views keep working unchanged.
Dual ingestion needs more resources. Plan for additional collector CPU and memory, ClickHouse CPU, and log disk space before you upgrade.
The migration guide has a query to estimate the disk increase.
Bug Fixes
- JSON log bodies and object fields now render properly in every logs view, instead of
[object Object]or a crash. HAVINGon formulas is now applied; it was previously accepted and ignored.- Time-shifted queries no longer return wrong data points when part of the time range is served from the cache.
- Logs and traces charts with a group-by and a limit now show the correct top groups. Previously, cached results could show the wrong groups or partial series.
- The Alert Details page no longer crashes when the URL has an invalid
relativeTime. It now falls back to the default 30-minute range. - Max lines per row in Logs now clamps to 1–10.
Maintenance
- Dashboards have a copy-ID button next to the title.
trace_id,span_id, and other high-cardinality fields can no longer be added as quick filters. Their values are unique per span or log, so the filter had nothing to pick from. They are removed from existing quick filters. You can still filter by them in the search bar.
⚠️ Action required (OSS users): Plan for extra capacity before upgrading
Log bodies are moving to native JSON storage (body_v2), which makes every field in a log body queryable by path and runs log queries faster over far less scanned data.
During the transition the collector writes each log body twice, to the existing body column and the new JSON column, so dashboards, alerts, and saved views keep working unchanged.
The migration guide has a query to estimate the disk increase. Details about this change are being tracked at SigNoz/signoz#13376.
⚠️ 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, orGET /api/v2/rulesneeds 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 oldersignoz_alertresource.
For UI-only users, no action is needed.
Check out the complete migration guide.
Scope roles by service and deployment environment
A role's telemetry selector can now grant access scoped to specific services (service.name) or environments (deployment.environment.name), not just a workspace key.
Give each team access to only the services it owns, or keep a role limited to staging while production data remains accessible only by administrators.
New scatter plot panel for dashboards

You can now use scatter plot dashboard panels to plot one metric against another with each point a series, like a service, route, region, or device, so correlations and outliers across many entities stand out at a glance.
Color points by a dimension, size them by a third metric for volume, and draw threshold lines to mark SLOs (for example, p95 latency vs error rate by country, or page load vs traffic by device).
Bug Fixes
- LLM spans that previously rendered empty strings now render the input and output messages sent by the Langfuse SDK.
- Three common ClickHouse SQL mistakes (bad reads, in-join-subquery denials, and decimal overflow) now come back as invalid-input errors with a suggested fix.
- Saved queries using the legacy
HAVINGfilter now work as intended. - Noz's
Open in Exploreraction now opens the result in the implied view, instead of always showing raw data. - Notification channel forms no longer cut-off on smaller screens.
Maintenance
- The Saved Views list no longer flashes a loading state on each row, and view names are now clickable links.
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, orGET /api/v2/rulesneeds 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 oldersignoz_alertresource.
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.
Bug Fixes
- Explorer links that carry a query the page can’t run, such as a ClickHouse query on the Logs Explorer, no longer crash the page. The Explorer now fills in any missing parts of the query, or resets it to the default query.
- Roles that were assigned to a deleted service account can now be deleted.
- For alerts with multiple queries, related logs and traces links in notifications and alert history now carry the query that breached the threshold. If the threshold uses a formula, the link carries all the queries in that formula.
- Planned downtimes now mute alerts correctly when the scope uses a dotted label, such as
cluster.name, that the alert doesn’t have.
Maintenance
- Notification Channels have been removed from the Settings menu. They’re still under Alerts, and
shift+g+nstill opens them.
⚠️ 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, orGET /api/v2/rulesneeds 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 oldersignoz_alertresource.
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.
Bug Fixes
- The Exceptions page now keeps your filter pills when you run the query.
⚠️ 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.
A rebuilt Dashboards panel editor

The dashboard panel editor has been rebuilt to make configuring and adding panels faster and easier to scan.
- The config pane is redesigned: collapsed sections show a one-line summary, a dot marks any section with non-default settings, every field has a
Resetlink, and visual choices are pick-from tiles that reflow with the pane. - Adding a panel now opens a searchable drawer with category filters and preview tiles, and lets you place the panel in a section, a new section, or the dashboard root.
- Panel titles now resolve dashboard variables (
$var,{{var}},[[var]]) in the header, the View modal, and download filenames. The title input now suggests variables after the$character.
New Heatmap panel for dashboards

Dashboards now support a Heatmap panel that shows how your data is distributed across buckets over time, with color encoding how many data points land in each bucket. It is built for distribution-shaped signals like request latency, where a single aggregated line hides the spread, so you can see where most values sit, how the distribution shifts, and when outliers spike.
Tune the color palette, opacity, and Y-axis scale from the panel editor, and use the legend search to filter across many groups.
Infrastructure Monitoring: Kubernetes status filters and related-resource navigation

You can now observe your Kubernetes workloads faster, with status filtering across list views and a quicker way to move between related resources.
- Kubernetes list views can now be filtered by pod status, node readiness, and container status.
- The Kubernetes side drawer gains an
Overviewtab that lists a resource’s related resources, so you can move between related entities, such as a node, its pods, and their containers, without leaving the drawer.
New onboarding integrations and simplified Android onboarding
You can now onboard 4 more data sources directly from SigNoz, including AI and agent tooling (Microsoft Agent Framework, Vercel Eve), runtimes and frameworks (Bun with Elysia), and network monitoring (SNMP). Each integration comes with its own guided setup so you can start collecting telemetry without hand-rolling the configuration.
The Java and Kotlin configurations now fall under a unified Android integration path, capturing key information in one central guide.
Bug Fixes
- Dynamic variables are now supported in Dashboard panel titles, restoring parity with earlier versions.
- A Home page crash caused by a load-animation race condition has been resolved.
- Truncated values in dropdowns now reveal the full text on hover.
- List views in Explorers now persist
Order Bysorting across back navigation, deeplinks, and saved views. - The log details header no longer shifts when you switch to the Context tab.
- PromQL queries using range functions like
max_over_timenow work as intended when transpiled series share labels.
⚠️ 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.
Create alerts and dashboard panels right from Explorer views

The Create alert and Add to dashboard actions are now available directly in the Logs, Traces, and Metrics Explorer views, in the view headers and per chart in metrics, so you can turn the query you're looking at into an alert or a dashboard panel without leaving the explorer.
Bug Fixes
- Password reset errors now clear as soon as you fix the password, instead of lingering after it's valid.
⚠️ 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.
Chart UX improvements

A few improvements now make charts easier to read and work with:
- Searchable legends: when a chart's bottom legend has more series than fit, it now includes a search box and a
Showing N of M seriescount, so you can find a series without scrolling through all of them. - Cleaner tooltips: tooltips omit the date for points from today, showing just the time.
- Tighter bar spacing: bars in bar and histogram panels sit closer together for an easier read.
More onboarding integrations
You can now onboard 20 more data sources directly from SigNoz, including AI and agent tooling (Cursor, Cline, OpenAI Agents SDK, vLLM, SGLang), sandboxes and runtimes (E2B, Daytona, Modal, Podman), and infrastructure (Karpenter, EMQX, AWS RDS Aurora, GCP Cloud Storage). Each comes with guided setup so you can start collecting telemetry without hand-rolling the configuration.
Bug Fixes
- Charts no longer assign the red colour to unrelated series, reserving it for signalling errors.
Maintenance
- Quick filters sidebar now scrolls on its own instead of scrolling the whole page.
⚠️ 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.
Bug Fixes
- Chart legends no longer drop series or flicker when the browser window is resized.
- Chart tooltip labels no longer break mid-word when a row's value is long.
- Legend color markers no longer overlap the quick filter panel in the Logs Explorer.
- Dynamic variable dropdowns on dashboards now search beyond the first loaded batch of values.
- The Related Values section in dynamic variable dropdowns (scoped to your other variable selections) has been re-enabled.
- Errored dashboard panels no longer re-run their failed query every time you scroll them back into view.
Dashboards added as a resource in custom roles

You now get complete flexibility over the level of dashboard access you want to give each user. We’ve added Dashboards as a resource in custom roles.
Go to Custom Roles and configure permissions for viewing, editing, and deleting dashboards. You can also scope access to specific dashboards.
For example, a team member can have edit access to one set of dashboards, view access to another, and no access to the rest. This gives you full control over which dashboards each user or team can access and what they can do with them.
Text panel added as a panel type in Dashboards

You can now add context, instructions, or runbooks alongside charts in your dashboards.
Text panels support Markdown features such as headings, lists, tables, links, and code blocks. Dashboard variables also work inside the text, so a variable like $service will update when you change the variable selection.
You can also use task lists in the panel, which can be useful for things like on-call checklists.
Improved panel chart legend controls
Chart legends are now more interactive. It's easier to investigate across multiple series in a panel.
Click any series in the legend to isolate it or hide it from the chart. Click another series to move the isolation, or use + to add the series to the panel. Hover over any series to highlight it while dimming the rest. You can also bring a hidden series back or copy its full name.
At least one series will always be visible in the chart. The right-side legend shows how many series are currently displayed.
⚠️ 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.
Bug Fixes
- Fixed the 'Open in new tab' setting for dashboard panel links. Previously, links always opened in a new tab regardless of the toggle. They now open in the same or a new tab based on the selected setting.
- The Duration section's reset in Quick Filters is fixed. Clicking it now resets the Duration filter.
Maintenance
- Quick Filter sections now show search and reset icons on hover only to make the sidebar cleaner. This replaces the always-visible search box. Also, the reset option is now available on every section. Earlier, it was available on active filters only.