skills.rest
tsuga-dev
tsuga-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

tsuga-debug-no-data

Diagnose missing Tsuga telemetry by validating OTLP export and service.name configuration.

2|Updated May 28, 2026
Search Tags:#observability#opentelemetry#sampling#tsuga#otlp debugging#telemetry triage#ingestion auth
One-click install
npx skills add https://github.com/tsuga-dev/agent-plugins --skill tsuga-debug-no-data
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tsuga-debug-no-data
Source: https://github.com/tsuga-dev/agent-plugins/tree/main/plugins/telemetry/skills/tsuga-debug-no-data
Command: npx skills add https://github.com/tsuga-dev/agent-plugins --skill tsuga-debug-no-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you diagnose why no telemetry (traces, metrics, and/or logs) is appearing in Tsuga, even though your service is expected to be exporting OTLP data.

Core Features & Use Cases

  • Fast signal triage: Checks whether Tsuga sees the service at all and whether specific signal types are missing, sparse, or present.
  • OTLP and resource validation: Verifies the configured OTLP endpoint, protocol, and required ingestion auth header expectations, and checks that the service.name resource attribute matches.
  • Common “it stopped exporting” root causes: Guides investigation through sampling settings, exporter shutdown/flush behavior, and network/TLS/auth reachability.

Quick Start

Tell the Skill your Tsuga service name and language/runtime, then ask it to debug why no traces, metrics, and logs are showing after your latest deploy.

Frequently Asked Questions about tsuga-debug-no-data

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

FAQPage Schema
Why are my OpenTelemetry traces and metrics not showing up in Tsuga after deploying?▼

Missing Tsuga telemetry signals can result from OTLP endpoint or protocol misconfiguration, a mismatched service.name resource attribute, or incorrect ingestion auth headers preventing data from reaching the backend.

How do I debug missing OTLP telemetry signals when my service is not visible in Tsuga?▼

Debug missing OTLP telemetry by performing Tsuga smoke checks to confirm service presence, then validating the OTLP endpoint, protocol, and required ingestion auth headers against your deployed OpenTelemetry SDK configuration.

What causes OpenTelemetry SDK telemetry to stop exporting suddenly after working previously?▼

Sudden export failures are typically caused by changes to sampling settings, exporter shutdown or flush behavior, or network and TLS reachability issues blocking the OTLP export pipeline.

Does my OpenTelemetry SDK service.name need to match the Tsuga service name exactly?▼

Yes, the service.name resource attribute configured in your OpenTelemetry SDK must match the expected Tsuga service name exactly, as mismatches prevent Tsuga from correlating and displaying the incoming telemetry signals.

What ingestion auth header is required to export OTLP data to Tsuga?▼

Tsuga requires specific ingestion auth headers in your OTLP export configuration to authorize incoming telemetry data, and missing or malformed headers will cause silent data rejection without visible export errors.

How do I check if sampling configuration is causing sparse or missing traces in Tsuga?▼

Check your OpenTelemetry SDK sampling settings to verify the sampling ratio is not zero or excessively low, as restrictive sampling configurations will drop traces, metrics, and logs before they reach the OTLP exporter.

Related Skills

Explore More Software Engineering Skills→
MakisuoMakisuo
1.6k

maple-kotlin-style

Instrument Kotlin Maple services with OpenTelemetry traces, metrics, and logs via OTLP.

Community
Intermediate
1k-off1k-off
1

opentelemetry

Implement OpenTelemetry instrumentation and OTLP pipelines for Grafana telemetry.

Community
Advanced
raphaelmansuyraphaelmansuy
2

otel-observability

Enable OpenTelemetry traces, metrics, and logs across AgentStack components.

Community
Advanced
fmindfmind
1.4k

MLOps Observability

Configure ML observability with MLflow, Evidently, and SHAP for drift detection and alerting.

Community
Advanced