Skip to content
Back to skills

Distributed Tracing

ASecurity

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.

  • 508 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 7, 2026
developmentgodockerkubernetesdebuggingperformance

Security analysis

A100/100

Pro scans all 15 files and shows the line behind each finding

Scanned September 7, 2026

npx -y skills add Dokhacgiakhoa/antigravity-ide --skill distributed-tracing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Distributed Tracing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Distributed Tracing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dokhacgiakhoa-distributed-tracing/badge)](https://www.skillsdirectory.com/skills/dokhacgiakhoa-distributed-tracing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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](./sub-skills/trace-structure.md)
### 2. [Key Components](./sub-skills/key-components.md)
### 3. [Kubernetes Deployment](./sub-skills/kubernetes-deployment.md)
### 4. [Docker Compose](./sub-skills/docker-compose.md)
### 5. [OpenTelemetry (Recommended)](./sub-skills/opentelemetry-recommended.md)
### 6. [HTTP Headers](./sub-skills/http-headers.md)
### 7. [Propagation in HTTP Requests](./sub-skills/propagation-in-http-requests.md)
### 8. [Kubernetes Deployment](./sub-skills/kubernetes-deployment.md)
### 9. [Probabilistic Sampling](./sub-skills/probabilistic-sampling.md)
### 10. [Rate Limiting Sampling](./sub-skills/rate-limiting-sampling.md)
### 11. [Adaptive Sampling](./sub-skills/adaptive-sampling.md)
### 12. [Finding Slow Requests](./sub-skills/finding-slow-requests.md)
### 13. [Finding Errors](./sub-skills/finding-errors.md)
### 14. [Service Dependency Graph](./sub-skills/service-dependency-graph.md)
### 15. [Correlated Logs](./sub-skills/correlated-logs.md)

Files in this skill

  • SKILL.md2.1 KB
  • sub-skills/adaptive-sampling.md225 B
  • sub-skills/correlated-logs.md946 B
  • sub-skills/docker-compose.md482 B
  • sub-skills/finding-errors.md102 B
  • sub-skills/finding-slow-requests.md83 B
  • sub-skills/http-headers.md122 B
  • sub-skills/key-components.md262 B
  • sub-skills/kubernetes-deployment.md546 B
  • sub-skills/opentelemetry-recommended.md4 KB
  • sub-skills/probabilistic-sampling.md104 B
  • sub-skills/propagation-in-http-requests.md469 B
  • sub-skills/rate-limiting-sampling.md115 B
  • sub-skills/service-dependency-graph.md670 B
  • sub-skills/trace-structure.md223 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…