distributed-tracing

Name: distributed-tracing
Availability: InStock
Author: InnerScopeHearing

Monitor and analyze request flow across microservices using Jaeger and Tempo.

Updated May 30, 2026

Search Tags:#microservices #performance monitoring #Jaeger #distributed tracing #error propagation

Ready to run

npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill distributed-tracing-innerscopehearing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: distributed-tracing
Source: https://github.com/InnerScopeHearing/otchealth-claude-tools/tree/main/skills/distributed-tracing
Command: npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill distributed-tracing-innerscopehearing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Jaeger, Tempo, OpenTelemetry, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the challenge of understanding and debugging the flow of requests across microservices, helping to identify performance bottlenecks and error propagation.

Core Features & Use Cases

Trace Request Flow: Visualize the journey of requests across multiple services.
Performance Monitoring: Track latency and dependencies to find and fix issues.
Error Propagation: Quickly identify where and why errors occur in a distributed system.
Use Case: If you are experiencing slow response times or unhandled exceptions in your microservices architecture, this Skill can help you pinpoint the root cause.

Quick Start

To begin using distributed tracing, execute the following command in your terminal: ./scripts/start-tracing.sh

Frequently Asked Questions about distributed-tracing

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

FAQPage Schema

How does distributed tracing help debug slow microservices?▼

Distributed tracing helps debug slow microservices by visualizing the journey of requests across multiple services, tracking latency and dependencies to pinpoint performance bottlenecks and error propagation.

How do I trace request flow across microservices using Jaeger and Tempo?▼

You can trace request flow across microservices using Jaeger and Tempo by running the initialization script provided, which sets up the environment to monitor and analyze the flow of distributed requests.

Do I need OpenTelemetry to monitor microservices with distributed tracing?▼

Yes, you need OpenTelemetry for instrumentation, along with Jaeger and Tempo setup, to effectively monitor and analyze the flow of requests across your microservices architecture.

Can I identify error propagation in a distributed system with this setup?▼

Yes, you can quickly identify where and why errors occur in a distributed system by using distributed tracing to track the flow of requests and visualize dependencies across services.

What is the best way to monitor performance bottlenecks in microservices?▼

The best way to monitor performance bottlenecks is by using distributed tracing tools like Jaeger and Tempo to track latency, visualize request journeys, and identify root causes of slow response times.