SigNoz review

SigNoz is an observability platform, not an instrumentation library or command-line tool. Teams send telemetry to SigNoz Cloud or operate the open-source Community edition on their own infrastructure. It sits downstream of application instrumentation and collection: the homepage recommends OpenTelemetry instrumentation or the OpenTelemetry Collector, with a SigNoz Helm chart for Kubernetes and a route for AWS CloudWatch logs.

The platform brings APM, logs, traces, infrastructure monitoring, alerts, and dashboards into one place. Its columnar datastore supports high-cardinality observability data, and teams can query through the query builder, PromQL, or ClickHouse SQL. Logs have trace correlation, while traces can be loaded and analyzed with up to a million spans. That makes SigNoz a central store and investigation interface for service and infrastructure telemetry. It is not automatically a replacement for every existing monitoring component: teams still need to validate their collection paths, alert workflows, and operational requirements.

SigNoz's primary integration surface is OpenTelemetry: instrument applications or send data through the OpenTelemetry Collector. The homepage does not name programming languages or SDK packages, so check the vendor's documentation for language-specific instrumentation and supported exporters before choosing an implementation. The stated setup paths also include a Helm chart for collecting Kubernetes metrics, logs, and traces, and routing AWS CloudWatch logs to SigNoz Cloud.

For analysis, developers can use the query builder, PromQL, and ClickHouse SQL. The vendor points to a complete documentation index through llms.txt and says Markdown versions are available by appending .md to documentation URLs. For agent workflows, SigNoz offers an MCP server to bring telemetry into coding agents; Noz, inside SigNoz Cloud, can investigate incidents, tune alerts, and build dashboards. Confirm the precise MCP and telemetry integration requirements in the docs. The published product details do not identify a CLI or a general-purpose REST API, so verify those surfaces with the vendor if your deployment depends on them.

Self-Hosted SigNoz (Community) is the open-source option and has no listed software price. The cost is the infrastructure and operations needed to run it. SigNoz Cloud's Teams plan starts at $49 per month, and that monthly minimum includes $49 of usage. Above the minimum, logs and traces cost $0.30 per GB and metrics cost $0.10 per million samples. There is no host- or teammate-based charge, and the plan includes unlimited teammates and hosts.

Eligible startups can pay $19 per month for the first 12 months, including $19 of telemetry usage. Enterprise starts at $4,000 per month; Dedicated Cloud includes up to $4,000 in monthly ingestion usage. Enterprise also offers cloud, BYOC, or self-hosted deployment, volume discounts, annual contracts, dedicated support, and guided migration. The vendor lists no annual price for Teams or Enterprise. Model logs, traces, and metric samples using the pricing calculator, and account for usage above the included minimum. The pricing page lists no separate rate-limit fee or numeric rate limit; ask about ingestion controls and any deployment-specific constraints.

SigNoz offers an open-source Community edition that teams can self-host and self-manage, as well as cloud and Enterprise deployment options. The available product details do not name the open-source licence, so check the current repository licence before modifying, redistributing, or embedding the software. Enterprise options include cloud, BYOC, and self-hosted deployments.

OpenTelemetry is a meaningful portability point: the vendor positions it as an open standard that can keep instrumentation portable as a stack changes. That does not by itself guarantee a simple exit. Confirm how to export stored logs, metrics, traces, dashboards, and alert definitions, and test whether your current telemetry pipeline can route to another backend. The product details do not describe export formats or a migration procedure. With self-hosting, teams control their deployment environment but take responsibility for operating the stack; cloud users should confirm data access and export terms before relying on the service.

SigNoz lists SOC 2 Type II and HIPAA compliance and offers Enterprise deployment choices that include dedicated cloud and BYOC. Confirm which regions, controls, contracts, and features apply to your plan before sending regulated data. The homepage describes traces with up to a million spans, but that is not an ingestion-rate or retention guarantee. Ask the vendor for applicable rate limits, retention terms, service-level commitments, and scaling guidance for your workload.

Self-hosted operators should plan for the observability stack's infrastructure and maintenance. A SigNoz maintainer described distributed ClickHouse support for running multiple shards to handle large ingestion rates; validate the current deployment guidance against your edition and scale. Reddit feedback is mixed: some users report successful Kubernetes deployments and useful capabilities, while others report intermittent behavior or object to identity features being gated. A later maintainer comment says Community edition added Google OAuth support, so verify current SSO providers and release status instead of relying on older reports. Model usage and set ingestion controls to limit noisy telemetry.