distributed-tracing
Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices.
Profile →npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ### Trace Structure ``` Trace (Request ID: abc123) ↓ Span (frontend) [100ms] ↓ Span (api-gateway) [80ms] ├→ Span (auth-service) [10ms] └→ Span (user-service) [60ms] └→ Span (database) [40ms] ``` ### Key Components - **Trace** - End-to-end request journey - **Span** - Single operation within a trace - **Context** - Metadata propagated between services - **Tags** - Key-value pairs for filtering -
- Do not use this skill when
- Instructions
- Purpose
- Use this skill when
- Distributed Tracing Concepts
- Trace Structure
- Key Components
- Jaeger Setup
- Kubernetes Deployment
- Docker Compose
- Application Instrumentation
- OpenTelemetry (Recommended)
- Context Propagation
- HTTP Headers
Deploy Jaeger Operator kubectl create namespace observability kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/download/v1.51.0/jaeger-operator.yaml -n observability Deploy Jaeger instance kubectl apply -f - <<EOF
What does the distributed-tracing skill do?
Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.