skills.rest
jamesaphoenix
jamesaphoenixCOMMUNITY
Explore all skills by this author →
Website𝕏@jamesaphoenix12GitHub

debug-from-telemetry

Correlate traces, logs, and metrics to diagnose distributed failures.

1|Updated Feb 20, 2026
Search Tags:#debugging#metrics#observability#trace#telemetry#distributed-systems#root-cause-analysis
One-click install
npx skills add https://github.com/jamesaphoenix/tx-agent-kit --skill debug-from-telemetry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-from-telemetry
Source: https://github.com/jamesaphoenix/tx-agent-kit/tree/main/.codex/skills/debug-from-telemetry
Command: npx skills add https://github.com/jamesaphoenix/tx-agent-kit --skill debug-from-telemetry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug failures by correlating traces, logs, and metrics across services to surface root causes quickly.

Core Features & Use Cases

  • Correlate traces with adjacent logs to align events across distributed systems.
  • Identify latency hotspots and error spikes by cross-referencing metrics and traces.
  • Use case: when a request trips across several services, trace IDs help you pinpoint where latency grows and where failures originate.

Quick Start

Query a failing trace, then correlate logs and metrics to identify the root cause.

Frequently Asked Questions about debug-from-telemetry

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

FAQPage Schema
How do I debug distributed failures by correlating traces, logs, and metrics?▼

Debug distributed failures by querying a failing trace, then cross-referencing adjacent logs and metrics to pinpoint where latency grows and errors originate across services.

How does trace correlation identify latency hotspots in microservice architectures?▼

Trace correlation identifies latency hotspots by mapping trace IDs across microservice architectures, cross-referencing metrics to surface exactly where latency grows and failures originate.

Can I use this with OpenTelemetry-style traces and existing observability tooling?▼

Yes, it supports OpenTelemetry-style traces, log correlation, and metrics-based analysis with direct integration into existing observability tooling for microservice architectures.

What is the best way to find the root cause of error spikes across services?▼

The best way to find the root cause of error spikes is cross-referencing metrics and traces to align events across distributed systems, surfacing where failures originate quickly.

When do I need telemetry debugging for distributed systems?▼

You need telemetry debugging when a request trips across several services and you must use trace IDs to correlate logs and metrics to identify the root cause.

Why does trace and log correlation fail to pinpoint failures in microservices?▼

Trace and log correlation fails to pinpoint failures when telemetry data is not properly aligned across distributed systems, preventing accurate cross-referencing of metrics and traces.

Related Skills

Explore More Software Engineering Skills→
emilneuraz-aiemilneuraz-ai

python-observability

Instrument Python applications with OpenTelemetry for structured logs, metrics, and traces.

Community
Advanced
unblockedunblocked
13

headless-recommend-fixes

Generate ranked remediation options for incidents from parsed context and historical fixes.

Official
Advanced
ToanPV90ToanPV90

opentelemetry

Configure OpenTelemetry collectors and instrumentation for distributed tracing and metrics.

Community
Advanced
dseirz-rgbdseirz-rgb

multi-service-debug

Correlate logs and traces to diagnose cross-service failures between Vercel and Cloud Run.

Community
Advanced