distributed-tracing

version	4.1.0-fractal
name	distributed-tracing
description	Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.

Distributed Tracing

Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices.

Do not use this skill when

• The task is unrelated to distributed tracing
• You need a different domain or tool outside this scope

Instructions

• Clarify goals, constraints, and required inputs.
• Apply relevant best practices and validate outcomes.
• Provide actionable steps and verification.
• If detailed examples are required, open resources/implementation-playbook.md.

Purpose

Track requests across distributed systems to understand latency, dependencies, and failure points.

Use this skill when

• Debug latency issues
• Understand service dependencies
• Identify bottlenecks
• Trace error propagation
• Analyze request paths

Distributed Tracing Concepts

🧠 Knowledge Modules (Fractal Skills)

1. Trace Structure

2. Key Components

3. Kubernetes Deployment

4. Docker Compose

5. OpenTelemetry (Recommended)

6. HTTP Headers

7. Propagation in HTTP Requests

8. Kubernetes Deployment

9. Probabilistic Sampling

10. Rate Limiting Sampling

11. Adaptive Sampling

12. Finding Slow Requests

13. Finding Errors

14. Service Dependency Graph

15. Correlated Logs