Skip to main content

SigNoz

Overview​

SigNoz sends logs, metrics, and traces to SigNoz using the OpenTelemetry Protocol (OTLP). In the Praxis catalog this appears as a dedicated observability destination; the pipeline compiles to the same OpenTelemetry OTLP exporter as the generic OTLP destination (gRPC or HTTP, depending on protocol in your config).

Supported types: Logs · Metrics · Traces

Configuration​

All fields—protocol (grpc or http), gRPC/HTTP endpoints, compression, TLS, custom headers, sending queues, retries, and authentication (Noauth, OAuth2, and other supported credential types)—are identical to the OTLP destination. See the full reference: OTLP destination.

Notes for SigNoz​

  • Point grpc_endpoint or http_endpoint at your SigNoz OTLP ingress (host and port from your self‑hosted or cloud deployment). Many self-hosted installs expose OTLP on 4317 (gRPC) and 4318 (HTTP); confirm the values for your environment.
  • If your SigNoz tier requires an ingestion key or other metadata, add it with gRPC headers or HTTP headers in the destination configuration, or use a credential type your organization standardizes on.
  • For TLS to internal collectors, use the gRPC TLS or HTTP TLS sections in the OTLP doc as needed.

External documentation​