SigNoz
Docs
PricingCustomer Stories
Docs
IntroductionContributingMigrate from DatadogSigNoz API
Community
Support
Slack
Twitter
Launch Week
Changelog
Dashboard Templates
DevOps Wordle
Newsletter
More
SigNoz vs DatadogSigNoz vs New RelicSigNoz vs GrafanaSigNoz vs Dynatrace
Careers
AboutTermsPrivacySecurity & Compliance
SigNoz
All systems operational

Changelog

Follow us on LinkedIn
Back to all posts
July 02, 2025

🚨 Important: Migration Required (Community Edition)

We're migrating from underscore-based metric names (system_memory_usage) to dot-based metric names (system.memory.usage) to align with OpenTelemetry semantic conventions. This gives you better namespacing and improved compatibility across all your observability signals.

What you need to do: Your existing alerts and dashboards need to be migrated to use the new dot-based metric names. We've created migration scripts that handle this automatically for you.

The migration is a one-time process and the scripts are safe to run multiple times. We support all deployment types: Kubernetes, Docker, and Linux binary installations.

Migration Guide → Community Edition

🚨 Important: Migration Required (Cloud)

If you're using API keys to query metrics directly, you may need to update your integrations to reflect the new metric and label formats. For all other users, absolutely nothing. The migration is fully managed by our team, and your dashboards, alerts, and queries will continue to operate without any changes.

Migration Guide → Cloud

Trace Funnel Analytics

Your browser does not support the video tag.

Trace funnel feature is now complete with analytics APIs and queries. You can analyze user journeys and conversion funnels directly from your traces, including funnel validation, step-by-step analytics, and identification of slow or error traces in your user flows.

Visual Events on Span Waterfall & Flamegraph

Media

Span events now appear as blue indicators on the timeline in both waterfall and flamegraph views. You'll immediately spot where events occur within each span's execution. This was a highly requested feature from our cloud users.

Sidebar Revamp

Media

Decluttered sidebar with pinning options. You can now pin only what's important for your workflow and customize the navigation based on your needs.

In-App Changelog Notifications

Your browser does not support the video tag.

You'll now see changelog notifications right in your SigNoz dashboard when newer versions are available, starting with this update.

Bug Fixes

  • Fixed trace filters getting duplicated when switching between span scopes, improving trace analysis workflow reliability.
  • Resolved environment filter functionality in infrastructure monitoring for accurate resource filtering across all views.
  • Corrected stepInterval parameter not updating correctly in bar chart request payloads, ensuring proper time-based data visualization.
  • Eliminated flickering in logs explorer table view by setting proper column width constraints for better visual stability.
  • Resolved timestamp calculation for logs explorer chart and list queries to ensure accurate time range filtering and data retrieval.
  • Improved log details filters to properly use data types from log data response for more accurate filtering operations.
  • Resolved top-level keys EXIST and NOTEXIST filter simulation for improved log query accuracy.
  • Restored span links tab functionality in span details drawer for better trace correlation navigation.

Maintenance

Community Edition:

  • Issue #7976 - Completely removed the telemetry layer from the OSS build. This resolves issues where disabling telemetry still left background analytics running, causing ClickHouse query spikes and CPU issues. We have introduced a single, definitive configuration that governs analytics for the entire product: https://signoz.io/docs/telemetry/
  • Deprecated all command line flags in favour of supporting unified configuration management through a single config file in the future for a cleaner, more maintainable approach to setup and deployment. Previously, configuration was scattered across multiple methods, creating inconsistencies.
  • Updated opamp-go version with enhanced opamp server functionality, improved logging, and better connection handling.