You want an open-source license
The SigNoz community edition is MIT-licensed with no data cap. Diting is a commercial product and needs a license.
Diting vs SigNoz
SigNoz puts OpenTelemetry, ClickHouse and a clean console together well. The real difference is how data gets in, and what you can do once a problem is on screen.
If your teams already run OpenTelemetry end to end and can own the collectors and ClickHouse, SigNoz is a good fit.
Where SigNoz fits better
OTel is already everywhere
Services, gateways and frontends already send OpenTelemetry signals and only need a backend. SigNoz plugs straight in.
You want to run it lean
Your team can own ClickHouse, collectors and upgrades, and you want a cloud option for when you do not.
Line by line
| Question | Diting | SigNoz | Who's ahead |
|---|---|---|---|
| Capture and intrusion | |||
| Application changes | None. Capture happens on the host | Needs an OpenTelemetry SDK or auto-instrumentation | Diting |
| Components to install | One host agent | OTel Collector plus per-service SDKs | Diting |
| Restart to onboard | No restart | Agents and services usually restart | Diting |
| Old kernels and domestic distros | 3.10 and up, 12 validated distributions | No kernel-version commitment; validate against OTel and your distro | Diting |
| Where protocols are parsed | In the agent, 18 L7 protocol families | In the application, coverage follows the SDK | Diting |
| Frontend replay injection | Agent injects at nginx or the container layer | No RUM, no session replay | Diting |
| Deployment and data ownership | |||
| Self-hosted | Single node, cluster and HA | Community self-host, or SigNoz Cloud | Even |
| Runs fully disconnected | Install, upgrade, license and AI models ship in the bundle | Community edition can run air-gapped with images you prepare | Even |
| Outbound network | None | None for self-hosted; Cloud reports out | Even |
| Where data lives | Your own ClickHouse | Your own ClickHouse, or SigNoz Cloud | Even |
| Offline upgrade and rollback | Offline bundle, rollback supported | You build images and charts; rollback follows your own process | Diting |
| Licensing | Signed file, renewed offline | Community edition is MIT, no license fee | SigNoz |
| Observability | |||
| Logs, metrics, traces, topology | One capture, one timeline | Complete, aligned on OTel semantic conventions; service map is beta | Even |
| Database observability | 6 databases parsed on the wire, no driver | No | Diting |
| Kubernetes | 1.26–1.33, 20+ resource pages | Node and pod metric dashboards; no resource-level action pages | Diting |
| Kernel observability | 26 capabilities, 3.10–5.17 | No | Diting |
| Locate and review | |||
| Alerting and impact paths | Topology, impact paths, alerts | Threshold, anomaly and Apdex alerts; no impact-path analysis | Diting |
| Session replay joins the trail | SQL, trace, log and recording jump into each other | No | Diting |
| Profiles and kernel hotspots | Profiles and kernel hotspots side by side | No | Diting |
| Actions and automation | |||
| Batch runs and terminals | Batch execution, file distribution, remote terminal | No | Diting |
| Chaos experiments | 36 actions on the same timeline as signals | No | Diting |
| CI/CD and app platform | Pipelines, releases, rollback, app platform | No | Diting |
| Security and access | |||
| Permission granularity | RBAC down to buttons, enforced server side | Fixed roles, custom roles in beta, no button-level permissions | Diting |
| Audit and masking | Every action audited; replay input masked | No audit logs; masking needs a self-built log pipeline | Diting |
Common questions
- SigNoz is free. Why pay for Diting?
- The software is free; the work is not. Instrumentation, ClickHouse operations, offline upgrades and action after an alert still land on someone. If your team can carry all of that, SigNoz is the cheaper route.
- Can we keep our OTel data?
- Yes. The Diting gateway accepts OTLP, so the existing collector can dual-send before anything is removed.
- What happens to our history?
- Keep SigNoz read-only during the parallel period. Export what must be kept and write it across as needed. Diting does not promise a lossless move.
- Do dashboards and alerts need rebuilding?
- Yes. Move one board on non-critical services first, land the rules on Diting topology and logs, then widen.
- How far back do old kernels go?
- There is a compatibility path from 3.10, with each capability reported. What is limited is written down, not marked as supported.
Vendor information comes from public vendor pages, checked November 2026. Products and pricing follow their official pages.SigNoz docsSigNoz pricing
Bring your system in
Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.