What SigNoz/signoz shipped
Written by FoxPlug from the repository's own releases; not affiliated with Signoz. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/SigNoz/signoz; Signoz did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- Release v0.149.0 shipped, and log bodies begin moving to native JSON storage with dual ingestion that needs extra collector CPU and memory, ClickHouse CPU and log disk space. Release
- The alert rules list now uses the server-side rules endpoint, so filtering, sorting and pagination run on the backend, and the search bar takes filter DSL with autocomplete. Pull request #13322
- The Jira notification channel now supports self-hosted Jira Server and Data Center version 8.14 or newer, with a personal access token instead of email and API token. Pull request #13424
- A geo map panel kind was added: a scalar query joined into one row per location, with color and size from different queries, a 10,000 row limit, and placement by country, state or lat/lon. Pull request #13351
- Pie charts can now group small slices into an automatic Other slice: anything under 1 percent of the total joins Other, and a pie draws at most 15 slices. Pull request #13428
- Clicking a row in the traces explorer list now opens the span in a side drawer behind the TRACES_SPAN_DRAWER_ENABLED flag, instead of always opening the trace page. Pull request #13361
- Five more ClickHouse SQL mistakes caused by user SQL now return 400 with a suggestion instead of 500. Pull request #13444
- JSON log bodies and object fields now render on every logs surface, fixing crashes, object Object output and raw JSON wrappers in the Default view, Column and Raw, Live logs, the dashboard List panel and the pod Events tab. Pull request #13362
- The dashboard header has a copy button next to the title that copies the dashboard ID. Pull request #13404
- The e2e suite now runs on 10 shards instead of 4. Pull request #13395
Why it matters
This week brings a new release plus a storage change for log bodies that people planning upgrades need to size for. It also adds self-hosted Jira notifications, geo map panels and a traces span drawer, and turns several ClickHouse SQL mistakes into clear 400 responses instead of 500s.
Changelog entry
- Release v0.149.0: log bodies move to native JSON storage with dual ingestion, adding collector, ClickHouse and disk load. Release
- Alert rules list uses the server-side rules endpoint for filtering, sorting and pagination, with filter DSL search and autocomplete. Pull request #13322
- Jira notification channel supports self-hosted Jira Server and Data Center 8.14 or newer using a personal access token. Pull request #13424
- New GeoMapPanel dashboard kind places scalar query rows by country, state or lat/lon with a 10,000 row limit. Pull request #13351
- New GeoMap chart shades countries or states by value and draws bubbles and up to 100k lat/lon points, with bundled outlines and no tiles. Pull request #13350
- Pie charts group slices under 1 percent into an automatic Other slice and draw at most 15 slices. Pull request #13428
- Traces explorer list rows open a span details drawer behind the TRACES_SPAN_DRAWER_ENABLED flag. Pull request #13361
- Five more ClickHouse SQL errors now return 400 with a suggestion instead of 500. Pull request #13444
- JSON log bodies and object fields render correctly across logs views, Live logs, the dashboard List panel and the pod Events tab. Pull request #13362
- Dashboard header gets a copy button that copies the dashboard ID. Pull request #13404
- Query range offset now applies to scalar, time series, trace operator and formula results, not only raw and trace requests. Pull request #13436
- Alert Details falls back to the default 30m range when the URL relativeTime cannot be parsed, instead of hitting the error boundary. Pull request #13375
V0.149.0 is out. Log bodies start moving to native JSON storage with dual ingestion, so plan extra collector, ClickHouse and disk capacity. Also this week: self-hosted Jira, geo map panels, a spans drawer in the traces list, and clearer 400s for ClickHouse SQL mistakes.
Release v0.149.0 is out. Log bodies are moving to native JSON storage, and logs are dual-ingested from this release, which needs extra collector CPU and memory, ClickHouse CPU and log disk space, so plan capacity before upgrading. Also shipped: the alert rules list now filters, sorts and paginates on the server with filter DSL search; the Jira channel supports self-hosted Jira Server and Data Center 8.14 or newer with a personal access token; a geo map panel for dashboard queries; pie charts that group small slices into an automatic Other slice; a span details drawer in the traces explore list behind a flag; and five more ClickHouse SQL mistakes now return 400 with a suggestion instead of 500.
Week of October 26, 2026
What shipped
- Release v0.148.1 shipped with routing policies and planned downtime shown as tables. Release
- Release v0.148.0 shipped, including anomaly alerts in the new alert experience and saved views quick filter fixes. Release
- A scatter plot panel kind was registered for V2 dashboards, with editor controls for dimensions, axes, point size and opacity. Pull request #13051
- Notification channels, routing policies and planned downtime now sit under one configuration tab on the alerts page with a secondary sidebar. Pull request #13230
- Routing policies and planned downtime switched from collapsible cards to full-width tables with column pickers, sorting, row actions and empty states. Pull request #13259
- Deleting a service account now also deletes its role mappings so the assigned roles can be removed. Pull request #13266
- Explorer links carrying an unsupported query in the URL are repaired instead of crashing the page or running the wrong query. Pull request #13257
- Webhook authentication in notification channels is chosen with a radio, and the Google Chat, Jira and incident.io URL checks were dropped. Pull request #13276
- New anomaly alerts are created in the new alert form and saved as v2alpha1. Pull request #13130
- Thread tab switching now adds a browser history entry so going back returns to overview, and the thread empty state links to the updated docs path. Pull request #13229
Why it matters
This week brought two releases and a move of alerting configuration into one place, with routing policies and planned downtime now in full-width tables that show more fields at once. Dashboards gained a scatter plot panel kind, and several fixes address real friction: deleted service accounts freeing their roles, malformed explorer links no longer crashing the page, and webhook auth being simpler to set up.
Changelog entry
- Release v0.148.1. Release
- Release v0.148.0. Release
- Add the scatter plot panel kind to V2 dashboards with editor controls. Pull request #13051
- Add the scatter chart layer with quadtree hover and click hit-testing. Pull request #13050
- Consolidate notification channels, routing policies and planned downtime under one configuration tab. Pull request #13230
- Show routing policies and planned downtime as full-width tables with column pickers and row actions. Pull request #13259
- Create anomaly alerts in the new alert form and save them as v2alpha1. Pull request #13130
- Delete service account role mappings when a service account is deleted. Pull request #13266
- Repair unsupported composite queries in explorer URLs instead of crashing. Pull request #13257
- Pick webhook auth with a radio and drop the Google Chat, Jira and incident.io URL checks. Pull request #13276
- Thread tab switches add a history entry and the empty state links to the updated docs path. Pull request #13229
- Saved views header name opens and closes the views panel, with quick filter fixes. Pull request #13232
This week: v0.148.0 and v0.148.1 released. Alerting configuration now lives in one tab, routing policies and planned downtime are tables, V2 dashboards get a scatter plot panel, and service account deletion now removes its role mappings.
This week shipped two releases, v0.148.0 and v0.148.1. Alerting configuration for notification channels, routing policies and planned downtime now sits in one tab on the alerts page, and routing policies and planned downtime are shown as full-width tables with column pickers, sorting and row actions. V2 dashboards gain a scatter plot panel with controls for dimensions, axes, point size and opacity. Fixes include service account deletion now removing its role mappings so roles can be freed, explorer links with unsupported queries being repaired instead of crashing, and webhook authentication picked with a radio.
Week of October 19, 2026
What shipped
- Released v0.147.0, which includes the Telegram notification channel form, fine-grained authorization on metrics explorer routes, logs enabled for the GCP integration, and notification channel changes. Release
- Added a Telegram notification channel form with bot token, numeric chat id, optional forum topic id and message template, built against the v2 schemas. Pull request #13119
- Enabled fine-grained authorization on metrics explorer routes so a custom role scoped to a workspace key on metrics no longer lists, inspects or reads stats for every metric. Pull request #13150
- Enabled logs and added a collection strategy for the GCP integration in the manual flow. Pull request #13184
- Added client changes for the GCP integration agent flow, including the agent connection method, a create account form and a single connection command. Pull request #13159
- Added a thread tab to trace details that renders a trace's gen-ai spans as a conversation with infinite scroll in both directions and opens at a given span id. Pull request #13073
- Added Overview and Thread tabs to trace details, with the active tab kept in the URL, a shared header and a span detail variant hook. Pull request #13071
- Fixed scalar metric queries to apply the limit after reduceTo, so the correct groups are kept and rows are sorted by the shown value. Pull request #13083
- Fixed formula heatmaps on a linear axis so values at or below zero land in the zero bucket on both axes. Pull request #13217
- Changed the channel pickers on the alert rule form and routing policies to read the v2 list API and page instead of truncating, so orgs past the 200 limit stop losing channels. Pull request #13129
Why it matters
This week brought a release with Telegram notification channels, fine-grained authorization on metrics explorer routes and logs in the GCP integration. Several fixes landed for metric queries, formula heatmaps and anomaly alerts, and the notification channel screens and alert pickers moved further onto the v2 API. Trace details also gained an Overview and Thread tab for reading gen-ai spans as a conversation.
Changelog entry
- Release v0.147.0 with the Telegram channel form, FGA on metrics explorer routes, GCP integration logs and notification channel changes. Release
- Add a Telegram notification channel form with bot token, chat id, optional forum topic id and message template. Pull request #13119
- Enable fine-grained authorization for metrics explorer routes. Pull request #13150
- Enable logs and add a collection strategy for the GCP integration. Pull request #13184
- Add client changes for the GCP integration agent flow. Pull request #13159
- Add a thread tab to trace details rendering gen-ai spans as a conversation. Pull request #13073
- Add Overview and Thread tabs to trace details with the active tab in the URL. Pull request #13071
- Apply the limit after reduceTo for scalar metric queries. Pull request #13083
- Put non-positive formula heatmap values in the zero bucket on both axes. Pull request #13217
- Treat missing dotted labels as nil in downtime scope. Pull request #13118
- Keep the exceptions filter pills when running the query. Pull request #13204
- Read alert channel pickers from the v2 list API with paging. Pull request #13129
V0.147.0 is out with a Telegram notification channel form, fine-grained authz on metrics explorer routes and logs in the GCP integration. This week: a thread tab in trace details, scalar metric limits applied after reduceTo, and channel pickers now reading the v2 list API.
V0.147.0 shipped this week with a Telegram notification channel form, fine-grained authorization on metrics explorer routes, and logs enabled with a collection strategy for the GCP integration. Alongside it, trace details gained an Overview and Thread tab that renders gen-ai spans as a conversation. Scalar metric queries now apply the limit after reduceTo so the right groups are kept, and formula heatmaps put non-positive values in the zero bucket on both axes. The alert rule form and routing policy channel pickers now read the v2 list API and page instead of truncating at 200.
Week of October 12, 2026
What shipped
- Released v0.146.0, which includes ordering user log pipelines around signozlogsnormalizer, normalising
gen_aimessages in thread spans, support for AI queries in dashboards and variable support in panel titles. Release - Added a server-side clone endpoint for alert rules so callers pass only the source rule id and get back the newly created rule. Pull request #13093
- Removed the vulnerable v1 rule history endpoints that built ClickHouse queries from path and body fields with string formatting. Pull request #12163
- Opened the stats endpoint to every authenticated caller while keeping the response scoped to the caller's organization. Pull request #13152
- Saved views now enforce their list, create, read, update and delete permissions. Pull request #13027
- Infra monitoring routes now declare telemetry resource definitions across all 12 routes. Pull request #13143
- Time series and area panels now mark partial time buckets with a dotted ring. Pull request #13165
- Added an endpoint to index the JSON sub-columns of materialized attributes that already have a skip index. Pull request #13054
- The trace details waterfall filter now runs on
query_rangev5 with the typed expression passed as filter.expression scoped to the trace id. Pull request #13134 - Moved the app to @signozhq/ui 0.2.0 with breaking changes to button variants and colors. Pull request #12971
Why it matters
This week the release brings log pipeline ordering, normalized gen_ai messages in thread spans, AI queries in dashboards and variables in panel titles to users. Alert rules gain a server-side clone endpoint while vulnerable v1 rule history endpoints are removed, and saved views and infra monitoring routes now enforce permissions. Several trace detail formatters were added for different provider bodies, and charts now show partial buckets distinctly.
Changelog entry
- Released v0.146.0 with log pipeline ordering,
gen_aimessage normalization, AI queries in dashboards and variables in panel titles. Release - Added a server-side clone endpoint for alert rules. Pull request #13093
- Removed the vulnerable v1 rule history endpoints. Pull request #12163
- Opened the stats endpoint to every authenticated caller within their organization. Pull request #13152
- Saved views now enforce list, create, read, update and delete permissions. Pull request #13027
- Infra monitoring routes now declare telemetry resource definitions. Pull request #13143
- Time series and area panels now mark partial time buckets with a dotted ring. Pull request #13165
- Added an endpoint to index JSON sub-columns of materialized attributes with skip indexes. Pull request #13054
- Trace details waterfall filter now runs on
query_rangev5. Pull request #13134 - Updated to @signozhq/ui 0.2.0 with breaking button changes. Pull request #12971
- Query builder fields gained default placeholders, a default row limit and synced fields. Pull request #13113
- Added end-to-end tests for routing between pages. Pull request #13078
V0.146.0 is out with log pipeline ordering, gen_ai message normalization, AI queries in dashboards and variables in panel titles. This week also added server-side alert rule cloning, removed vulnerable v1 rule history endpoints, and put saved views and infra monitoring behind per
V0.146.0 shipped with log pipeline ordering around signozlogsnormalizer, normalized gen_ai messages in thread spans, AI query support in dashboards and dashboard variables in panel titles. Other changes this week: a server-side clone endpoint for alert rules, removal of the vulnerable v1 rule history endpoints, permission gating for saved views, and telemetry resource definitions on all infra monitoring routes. Charts now mark partial time buckets with a dotted ring, and trace details gained formatters for several provider payloads.
Week of October 5, 2026
What shipped
- Released v0.145.0, which includes a
json_body_dual_ingestionflag for dual body ingestion, semconv family resolution across logs and metrics, and page counts in the bottom strip for noz, alerts and home. Release - Added GET /api/v1/traces/{traceID}/summary, returning the trace header fields shown with the waterfall plus token and cost totals from a single query. Pull request #12911
- Added GET /api/v1/traces/{traceID}/thread, returning spans that carry input or output messages in timestamp order with cursor paging. Pull request #12999
- The traces attribute domain now supports per-path indexes, indexing promoted attributes on
attributes_promotedand unpromoted ones on attributes, and removed the prefix requirement in paths. Pull request #13021 - Refactored the promote module into a target-parameterized core so the logs body flow and new promotion domains share one implementation, adding spans attributes promotion endpoints. Pull request #12839
- Added saved views CRUD APIs for the alerts list page with GET and POST /api/v2/rule_views and PUT and DELETE /api/v2/rule_views/{id}. Pull request #12814
- Replaced the new-panel picker with a searchable drawer with category filters, preview tiles, and a footer that picks the target section or places the panel in the dashboard root. Pull request #12992
- Redesigned the panel editor config pane with one-line summaries for collapsed sections, dot markers for non-default settings, reset links, and grouped visual choices. Pull request #13010
- Added the heatmap chart layer, drawing a bucket by time density grid on canvas where cell colour is the observation count. Pull request #12775
- Added the heatmap panel to the v2 panel registry, wiring the chart layer to the heatmap request type and rendering the server grid without re-aggregation. Pull request #12789
Why it matters
This week adds trace summary and thread endpoints that the trace details header and waterfall can read from, reducing work done when opening a trace. Promotion and indexing for trace attributes now works per path, matching how logs bodies are handled. Dashboards gain a heatmap chart and panel plus a reworked panel picker and editor, and the alerts list page gains saved views.
Changelog entry
- V0.145.0:
json_body_dual_ingestionflag for dual body ingestion, semconv family resolution across logs and metrics, and page counts in the bottom strip. Release - Add GET /api/v1/traces/{traceID}/summary for trace header fields plus token and cost totals in one query. Pull request #12911
- Add GET /api/v1/traces/{traceID}/thread returning input and output message spans in timestamp order with cursors. Pull request #12999
- Support per-path indexes on trace attributes and remove the prefix requirement in paths. Pull request #13021
- Refactor path promotion into a target-parameterized core and add spans attributes promotion endpoints. Pull request #12839
- Add saved views CRUD APIs for the alerts list page: GET/POST /api/v2/rule_views, PUT/DELETE /api/v2/rule_views/{id}. Pull request #12814
- New-panel picker is now a searchable drawer with category filters, preview tiles and section placement. Pull request #12992
- Panel editor config pane redesign: section summaries, non-default markers, reset links and grouped visual choices. Pull request #13010
- Add heatmap chart layer drawing a bucket by time density grid on canvas. Pull request #12775
- Add signoz/HeatmapPanel to the v2 panel registry, rendering the server bucket grid. Pull request #12789
- Filter Kubernetes lists by pod status, node readiness and container status. Pull request #12946
- Add an Overview tab to the Kubernetes side drawer listing resources related to the entity. Pull request #12948
This week in SigNoz: v0.145.0 released. New trace summary and thread endpoints. Per-path indexes for trace attributes. Saved views APIs for the alerts list. A heatmap chart layer and panel in dashboards. New-panel drawer and redesigned panel editor. Kubernetes status filters in i
This week in SigNoz: v0.145.0 shipped with a json_body_dual_ingestion flag for dual body ingestion, semconv family resolution across logs and metrics, and page counts in the bottom strip. Traces: a summary endpoint returns the header fields shown with the waterfall plus token and cost totals in one query, and a thread endpoint returns input and output message spans with cursor paging. Promote: trace attributes support per-path indexes, indexing promoted attributes on attributes_promoted and unpromoted ones on attributes, with the prefix requirement in paths removed. Alerts list: saved views CRUD APIs under /api/v2/rule_views. Dashboards: a heatmap chart layer and heatmap panel, a searchable new-panel drawer with section placement, and a redesigned panel editor config pane. Infra monitoring
Week of September 28, 2026
What shipped
- Logs and metrics now resolve semantic convention families behind the
resolve_semconv_familiesflag. Pull request #12870 - Fine-grained access control moved users API and password reset tokens onto resource-based authorization checks. Pull request #13020
- Added
json_body_dual_ingestionflag to write log bodies to both legacy and v2 columns during migration. Pull request #12831 - Create alert and add to dashboard actions moved from bottom bar into explorer views for logs, traces and metrics. Pull request #12981
- Page counts now display on the left of the bottom strip for noz, alerts, home, exceptions and services. Pull request #12963
- JSON span attribute reads in traces query builder gated behind
use_trace_attributes_jsonflag. Pull request #12966 - Cloud integration agent now tracks sync state to identify removed regions and avoid unnecessary AWS calls. Pull request #12991
- Notification channel validations relaxed to support proxies and relays instead of requiring vendor hostnames. Pull request #13008
- Notification channels now store v2 config separately in database to avoid round-trip issues with receivers. Pull request #12984
- Password reset page no longer replays stale error messages when fixing a weak password. Pull request #13035
Why it matters
This week brought improvements to authorization, semantic conventions support, and user experience refinements. Several foundational changes address data migration and API consistency that matter for deployments using proxies or integrating with cloud providers.
Changelog entry
- Semantic convention families now resolve on logs and metrics (behind
resolve_semconv_familiesflag, default off) Pull request #12870 - Users API and reset password tokens moved to fine-grained access control with ResourceDefs Pull request #13020
- Log body dual ingestion flag for migrating from legacy body to
body_v2column Pull request #12831 - JSON span attribute reads gated behind
use_trace_attributes_jsonfeature flag (default off) Pull request #12966 - Page counts now display on left of bottom strip for noz, alerts, home, exceptions, services Pull request #12963
- Create alert and add to dashboard actions moved into explorer views for logs, traces, metrics Pull request #12981
- Cloud integration agent tracks sync state to identify removed regions Pull request #12991
- Notification channels relaxed to support proxies and relays instead of vendor hostnames Pull request #13008
- Notification channels store v2 config separately to eliminate receiver round-trip issues Pull request #12984
- Password reset page clears stale error messages when fields are corrected Pull request #13035
- Token idle expiry now works on Postgres after fixing timestamptz column persistence Pull request #12982
- Azure Container Apps diagnostic setting now uses allLogs instead of rejected category names Pull request #13013
This week: semantic convention resolution for logs and metrics, fine-grained access control on users API, and cloud integration sync state tracking to reduce unnecessary AWS calls.
This week in SigNoz: semantic convention families now resolve across logs and metrics, users API migrated to resource-based authorization checks, notification channels support proxies without vendor hostname restrictions, and cloud integration tracks sync state to optimize region cleanup. Plus: create alert and add to dashboard actions now live in explorer views.
Week of September 21, 2026
What shipped
- Released v0.143.0 with AI Observability for monitoring LLM and agent workloads including token tracking, cost analysis, latency measurement, and error reporting across models and providers. Release
- Migrated saved views from v1 to v2 API across home, explorer, and column synchronization endpoints. Pull request #12970
- Moved notification channels UI to v2 API with a redesigned list interface, removing legacy v1 clients and type definitions. Pull request #12945
- Added new list API for alert rules with filter query DSL, state filtering, sorting, and offset pagination. Pull request #12780
- Enabled AI Observability by default, removing the feature flag. Pull request #12947
- Fixed page height calculation in the bottom strip layout so pages now size from the layout instead of guessing viewport height. Pull request #12940
- Improved query performance by rendering materialized existence checks as explicit comparisons instead of bare boolean columns. Pull request #12978
- Fixed quick filters sidebar scrolling issue where it was scrolling the entire page instead of just itself. Pull request #12915
- Restored related values and API search functionality in dynamic variable dropdowns that was lost in the V1 to V2 dashboard rewrite. Pull request #12935
- Deleted the old logs explorer page and removed legacy logs API clients and LogQL parser from the codebase. Pull request #12930
Why it matters
V0.143.0 brings dedicated AI Observability tooling for LLM workloads alongside API migrations to v2 endpoints for saved views and notification channels. The release also fixes layout rendering issues, improves query performance, and removes deprecated code paths to streamline the application.
Changelog entry
- AI Observability: overview dashboard for tokens, cost, latency, and errors; explorer for AI spans; attribute mapping for vendor message keys Release
- Saved views now read from /api/v2/saved_views endpoint Pull request #12970
- Notification channels migrated to /api/v2/notification_channels with redesigned list Pull request #12945
- New GET /api/v3/rules list API for alert rules with filtering, sorting, and pagination Pull request #12780
- AI Observability feature flag removed and enabled by default Pull request #12947
- Bottom strip layout now sizes pages from available layout space instead of viewport estimation Pull request #12940
- Materialized existence checks now render as explicit comparisons for better skip-index usage Pull request #12978
- Fixed quick filters sidebar scrolling behavior on traces, LLM observability, API monitoring, and exceptions pages Pull request #12915
- Restored related values and API search in dynamic variable dropdowns Pull request #12935
- Removed old logs explorer page and legacy logs API clients Pull request #12930
V0.143.0 ships dedicated AI Observability for LLM and agent workloads with token tracking, cost analysis, and error reporting. Plus new v2 APIs for saved views and alert rules, layout fixes, and performance improvements.
V0.143.0 is live. We've added dedicated AI Observability for LLM and agent workloads with overview dashboards, token and cost tracking, and explorer views by model, provider, and agent. Behind the scenes: migrated saved views and notification channels to v2 APIs, added new alert rules list API with filtering and sorting, fixed layout rendering and sidebar scrolling issues, and improved query performance. The AI Observability feature is now enabled by default.
Week of September 14, 2026
What shipped
- Released v0.142.0 with authorization in quick filters, improved dashboard chart legend interactions, text panel specs, additional v2 notification channel APIs, and heatmap support. Release
- Released v0.142.1 with AI field keys in order by and options, list-view attributes from JSON column, dashboard delete unsafe v2 method, and bug fixes. Release
- Default attribute mapping for span groups: llm, agent, and tool groups now ship as built-in defaults instead of requiring manual creation. Pull request #12809
- AI observability quick filters now load the
gen_aifilter set with their own dedicated API endpoints for scoped field suggestions. Pull request #12788 - Trace view becomes the default explorer view in AI observability with config-driven toolbar actions. Pull request #12796
- Added API to repair malformed notification channels created via v1 without requiring database migrations. Pull request #12910
- Tokenizer now defaults to opaque provider for revocable server-side tokens instead of JWT in new deployments. Pull request #12896
- Slack notification channels now support additional configuration options and webhook channels can run without auth. Pull request #12907
- Chart legend interactions revamped: row clicks now isolate or restore series with one explicit target replacing undiscoverable click areas. Pull request #12838
- V2 notification channel secrets marked with password format in OpenAPI schema to hint UIs to obscure sensitive fields. Pull request #12791
Why it matters
Two new releases shipped with substantial improvements to AI observability features and notification channel handling. The week focused on making defaults smarter (attribute mapping, tokenizer provider) and improving explorability through better quick filters, toolbar configuration, and UI interactions.
Changelog entry
- V0.142.0: Authorization in quick filters, dashboard chart legend interaction improvements, text panel spec, v2 notification channel APIs, and heatmap support Release
- V0.142.1: AI field keys in order by and options, list-view attributes from JSON column, dashboard delete unsafe v2, and bug fixes Release
- Default attribute mapping: llm, agent, and tool span mapper groups now ship as built-in defaults Pull request #12809
- AI observability processors enabled by default to populate metadata Pull request #12912
- AI observability quick filters now use dedicated
gen_aifilter set with scoped field suggestions Pull request #12788 - Trace view is now the default explorer view in AI observability with config-driven toolbar actions Pull request #12796
- Added API to repair malformed notification channels created via v1 Pull request #12910
- Tokenizer defaults to opaque provider for revocable server-side tokens instead of JWT Pull request #12896
- Slack notification channels support additional configuration options; webhook channels can run without authentication Pull request #12907
- Chart legend interaction: row clicks isolate or restore series depending on what is displayed Pull request #12838
- V2 notification channel secrets marked with password format in OpenAPI schema Pull request #12791
- Frontend changes for attribute mapping support Pull request #12908
- Order by and column picker added to AI observability trace view Pull request #12859
- Query builder prefers resource over context for ambiguous filter keys Pull request #12888
- Webhook notification channels accept Bearer/bearer/BEARER authorization in v2 API Pull request #12890
- JWT tokenizer requires secret configuration to prevent empty-key token vulnerability Pull request #12899
- Updated genai semantic conventions for AI observability Pull request #12905
- Added contributing documentation for sqlcompiler package Pull request #12869
- Field key and value suggestions now read through generated clients with AI-observability variant Pull request #12846
- Dropped app-side bulk-filtering override for ClickHouse Pull request #12886
V0.142.0 and v0.142.1 now available. Better AI observability defaults, improved legend interactions, notification channel repairs, and opaque tokens by default.
SigNoz v0.142.0 and v0.142.1 are live. This week's updates bring smarter defaults for AI observability (pre-configured span groups), improved dashboard interactions (revamped legend controls), better notification management (channel repair API, additional Slack options), and stronger security (opaque tokens now default instead of JWT).