signoz

Configure SigNoz observability with OpenTelemetry ingestion pipelines and alerting.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Samuelca6399/AbsolutelySkilled --skill signoz-samuelca6399
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signoz
Source: https://github.com/Samuelca6399/AbsolutelySkilled/tree/main/skills/signoz
Command: npx skills add https://github.com/Samuelca6399/AbsolutelySkilled --skill signoz-samuelca6399

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about signoz

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure the OpenTelemetry Collector to send traces, metrics, and logs to SigNoz?

To send traces, metrics, and logs to SigNoz, configure the OpenTelemetry Collector with OTLP exporters using gRPC or HTTP, and set up correct signal pipelines for ingestion. You must use your specific SigNoz ingestion endpoint and authentication key.

Why are my OpenTelemetry traces not showing up in SigNoz?

OpenTelemetry traces may not show up in SigNoz due to missing service.name attributes, gRPC port blocking on 4317/4318, or incorrect OTel Collector pipeline configuration. Verify your OTLP exporter endpoints and ensure proper ingestion authentication is set.

What is the best way to set up SigNoz observability on Kubernetes or Docker?

The best way to set up SigNoz observability on Kubernetes or Docker is through the self-hosted deployment path, which involves configuring the OTel Collector pipeline to ingest OpenTelemetry traces, metrics, and logs into a single backend.

Can I use the SigNoz Query Builder to create alerts for logs and metrics?

Yes, you can use the SigNoz Query Builder to build dashboards and panels, then configure alerts for logs, traces, and metrics. This enables comprehensive exception monitoring and alerting workflows within the SigNoz backend.

Does SigNoz Cloud require an ingestion key for OpenTelemetry data?

Yes, SigNoz Cloud onboarding requires a specific ingestion key and correctly configured OTLP endpoints. This authentication ensures your OpenTelemetry traces, metrics, and logs are securely ingested and queried within the platform.

What causes high-cardinality issues when sending hostmetrics to SigNoz?

High-cardinality issues when sending hostmetrics to SigNoz are caused by misconfiguration in the OTel Collector pipeline. Resolving frequent hostmetrics pitfalls and correctly setting service.name attributes prevents ingestion failures and query performance degradation.