tracing

Trace request flows across microservices using OpenTelemetry to diagnose latency and errors.

Updated Jun 5, 2026

Search Tags:#performance analysis #system monitoring #error diagnosis #OpenTelemetry #distributed tracing

Ready to run

npx skills add https://github.com/hung-phan/system-skills --skill tracing-hung-phan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tracing
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/performance/tracing
Command: npx skills add https://github.com/hung-phan/system-skills --skill tracing-hung-phan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires opentelemetry, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables you to diagnose complex issues in distributed systems, such as latency spikes, cascading failures, and mysterious errors, by providing a detailed view of the system's performance and interactions.

Core Features & Use Cases

Distributed Tracing: Tracks the flow of a request across multiple services and databases, providing a complete picture of system behavior.
Latency Analysis: Identifies slow operations and bottlenecks, allowing for targeted optimization.
Error Diagnosis: Helps locate the root cause of errors by providing a timeline of system events.

Quick Start

Start tracing a new request with the command /system-review trace my_request_id.

Frequently Asked Questions about tracing

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

FAQPage Schema

How does distributed tracing help diagnose microservices latency spikes?▼

Distributed tracing diagnoses microservices latency spikes by tracking a request's flow across multiple services and databases, identifying slow operations and bottlenecks to target for optimization.

Do I need OpenTelemetry to trace performance bottlenecks in microservices?▼

Yes, you need OpenTelemetry and compatible tracing infrastructure to track request sequences, measure latency, and correlate errors with specific service interactions.

How do I start tracing a request to find the root cause of an error?▼

Start tracing a request to find error root causes by running the command `/system-review trace my_request_id` to generate a timeline of system events and service interactions.

Can distributed tracing locate the root cause of cascading failures?▼

Distributed tracing locates the root cause of cascading failures by providing a detailed timeline of system events, correlating errors with specific service interactions across the distributed system.

What's the best way to track a request flow across multiple services and databases?▼

The best way to track request flow across multiple services and databases is distributed tracing, which provides a complete picture of system behavior and identifies performance bottlenecks.