Changelog

Bug Fixes

• Few UI/UX bugs in the Alert Configuration and common Dashboard views have been resolved.
• Formula queries now correctly apply ordering and limit for table, pie, and value panels.
• Recurring maintenance windows now correctly honour a given fixed time range.
• A cache memory leak has been fixed, preventing unbounded memory growth.

Maintenance

• All high-end and critical-severity Dependabot security alerts have been resolved, significantly reducing dependency risks.
• Compatibility for pnpm generate:api after the Orval v8 upgrade has been restored, keeping API client generation stable for contributors.
• Tooltip values are now sorted in descending order, making it easier to spot the highest values at a glance.

Bug Fixes

• Query results with ragged label sets across series now render correctly in scalar table conversions.
• Query builder now rejects invalid group by timestamp on timeseries requests instead of producing malformed queries.
• Version comparison on the status check now correctly strips the v prefix, so e.g. v0.50.0 and 0.50.0 are treated as equal.
• Host metrics no longer show -1 placeholder values for missing samples.

Maintenance

• Enabled transaction_mode=immediate on the SQLite store for more predictable write behavior under contention.
• Tooling and dependency updates: orval bumped for API client generation, ts-jest updated, and filter styles refreshed.
• Continued internal UI consolidation onto the @signozhq/ui design system with icons migrated off lucide-react and Ant Design, LoadingOutlined replaced with the SigNoz loader, and typography aligned to the shared library.
• Auditor now supports a file provider, letting operators persist audit events to a file destination which is useful for environments that already ship file-based logs to a SIEM.

Bug Fixes

• Span start times in the trace detail view now match the waterfall v2 behavior, removing inconsistencies between the two trace experiences.
• Several minor tooltip rendering issues across the UI have been resolved.

Maintenance

• Infrastructure Monitoring tables have been migrated to the new shared table component, continuing the list/detail consolidation work from v0.120.0.
• Frontend type-checking has been migrated from tsc to tsgo, significantly speeding up the developer feedback loop. The lint-staged integration has also been fixed.
• Auth domain configuration API responses are now properly nested, with consistent naming (Updateable → Updatable ) and an Identifiable returned on create, relevant if you consume the SigNoz API directly or generate clients from it.
• The OpenAPI schema definitions for AuthDomainConfig and PostableChannel have been corrected, fixing mismatches between the documented and actual response shapes.

Bug Fixes

• Dashboard Bar and Time Series panels now render correctly when groupBy data is missing, fixing crashes seen in panels created through LLM/MCP workflows.
• Unsupported ClickHouse and PromQL query types have been disabled for Anomaly Detection alerts.
• Several edge cases in the Alerts and Planned Downtime frontend flows, such as stale loading states, have been resolved.
• Operations on deleted service accounts now return a proper 404 Not Found HTTP response instead of 501 Not Implemented.

Maintenance

• Frontend internals were streamlined with remaining xstate usage replaced with plain React state and local dispatch helpers, light-mode specific styles cleaned up, and unused code deleted.
• The Trace Waterfall API was moved into the Trace Detail module, with improvements to handling of large traces, caching, and error resilience.
• Alerts and Planned Downtime frontend flows were migrated to generated clients, reducing custom API adapter code and improving consistency in error handling.
• Integration and E2E test infrastructure was consolidated under a shared pytest project with common fixtures, local backend-based E2E runs, and updated CI workflows.
• oxlint and oxfmt were added as frontend linter and formatter respectively, speeding up the developer feedback loop.
• The OpenTelemetry Collector was bumped to stable v0.144.3.

Bug Fixes

• Alert creation from dashboard panels now works correctly for non-builder query types.
• Styling regressions introduced during the AWS integration refactor have been fixed, including semantic token issues in affected UI surfaces.
• The HAVING filter in the Query Builder V2 now emits a valid NOT IN operator, fixing cases where selecting this operator produced malformed queries.

Maintenance

• Alerting and rule-management internals have been consolidated further, with AlertManager, Ruler, and planned maintenance handlers moved into signozapiserver and tighter OpenAPI validation added for rules and downtimes.
• The AlertManager backend has been extended to support templating and custom notifier flows, laying the groundwork for future alert customization.
• The frontend design token system has been moved toward semantic tokens, improving consistency across the UI and reducing styling drift.
• Frontend asset management has been hardened, with assets migrated to src/assets and new lint rules added to prevent unsupported asset references.
• Infrastructure Monitoring internals for Hosts and Kubernetes have been consolidated into shared list and detail components, improving consistency and making these views easier to maintain.
• Unused or deprecated internals have been cleaned up, including unused trace cache settings and other obsolete code paths.

Bug Fixes

• Routing policy expressions that reference undefined variables no longer fail validation. Variables can now be left undefined without blocking the expression from being saved.
• Queries using hasAll or hasAny filter operators now pass the value argument correctly, fixing cases where these filters returned incorrect results.
• Deleted service accounts now return a proper unauthenticated error code instead of a generic failure when their API key is used.

Maintenance

• The OpenTelemetry Collector has been upgraded to v0.144.3-rc.4.
• Cloud integration modules have been refactored with updated query parameter support and removal of deprecated underscore-prefixed attribute dashboards.
• SQLite connection max lifetime is now configurable, improving connection management under sustained load.
• Frontend onboarding data sources have been migrated from JSON to TypeScript, and asset imports now use the @ alias for cleaner path resolution.
• ClickHouse queries sent from dashboard panels are now obfuscated in telemetry to avoid leaking sensitive query content.

Bug Fixes

• The host list in Infrastructure Monitoring now correctly shows refresh status, and refresh interval queries no longer overlap with each other.
• Dormant metrics in the query range API now return a warning instead of an error, preventing unnecessary failures when querying metrics that haven't reported recently.
• Alert rules history no longer crashes when relativeTime is empty.
• Dashboard variables with special characters now fall back to the raw parameter if decodeURIComponent fails
• The having expression in the query builder now validates correctly before execution.
• Empty not() filter expressions are now handled gracefully instead of producing query errors.

Maintenance

• Cmd+click (or Ctrl+click) now works on all clickable items across the app, opening them in a new tab as expected.
• Deprecated v3/v4 rule format support and the v1 Metrics Explorer code have been removed.
• JSON Path indexing is now enabled for JSON log bodies, improving query performance on structured log data.

Bug Fixes

• Filtering traces by trace ID in the list view no longer returns duplicate spans or results from outside the selected time window. Previously, the trace_summary timerange override was applied incorrectly across query buckets, causing repeated and out-of-range results.
• Logs pipeline filters now correctly resolve manually entered attribute names that are not present in the filter suggestion dropdown. Previously, entering a field like ddtags Exists by hand would misclassify it as a column rather than an attribute, causing downstream processors such as regex parsers to fail silently.
• The normalize pipeline now runs first in the processing chain, ensuring consistent field formatting before other pipelines execute.
• PromQL queries that exceed the execution deadline now return a 504 Gateway Timeout instead of a misleading 400 Bad Request. The PromQL engine timeout is also now configurable via the prometheus.timeout setting (default: 2m).
• Charts on the Volume Details page in Infrastructure Monitoring now display proper legend labels instead of "undefined."
• Domain rows in External APIs now show a pointer cursor on hover, indicating they are clickable.
• Time series charts with isolated data points surrounded by null values on both sides render those points correctly instead of dropping them.
• Deleting an alert rule or planned maintenance entry that has associated dependencies no longer fails with a foreign key constraint error.
• Agent configurations no longer get stuck in the "In Progress" state indefinitely.
• Users with the Editor role can now access gateway APIs as expected.
• Checkout and billing errors now surface the actual downstream error message in the UI instead of a generic failure.

Maintenance

Patch release with internal fixes. No user-facing changes.

Bug Fixes

• The custom domain settings card (Cloud) no longer shows a confusing plan name label. The card now displays the workspace name and a copiable license key in the footer, and no longer renders empty space when no custom domain is configured.
• Querying a histogram metric that has not received data within the selected time range now returns a "not found" error with diagnostic details (including when the metric was last seen) instead of a generic "something went wrong" message.
• Switching a dashboard panel type from time series to table now loads the table data correctly. The right-side settings panel in edit mode is also scrollable again.
• Dashboard variables now retain their selected values when navigating back from the widget editor and when toggling between view and edit modes.
• Creating a new Slack notification channel no longer fails with a "no global Slack App URL set" error. This affected users who signed up before v0.115.0 and did not have an existing Slack channel configured.
• The default color for log severity_text entries (when no severity key is present) now uses a theme-appropriate background color, resolving poor contrast in dark mode.