What problem does it solve?
SigNoz setup and telemetry troubleshooting often stall teams because OpenTelemetry configuration, ingestion endpoints, and signal-specific workflows are hard to align correctly.
Core Features & Use Cases
- SigNoz deployment guidance: Choose SigNoz Cloud or self-hosted deployment paths and configure the right ingestion endpoint and authentication for each.
- OpenTelemetry instrumentation + routing: Configure OTLP exporters and the OTel Collector pipelines so traces, metrics, and logs consistently land in SigNoz.
- Dashboards, querying, and alerting: Build dashboards and panels with the SigNoz Query Builder, then configure alerts for logs, traces, and metrics.
- Common troubleshooting guardrails: Resolve frequent issues like missing service.name, gRPC port blocking (4317/4318), hostmetrics misconfiguration, and high-cardinality pitfalls.
Quick Start
Use the signoz skill to generate an OTEL Collector configuration that sends traces, metrics, and logs from your app to SigNoz Cloud using your ingestion key.