distributed-tracing · sickn33 — Claude Code skill: what it does, how to install
Guides distributed tracing setup with OpenTelemetry, Jaeger, and Tempo across microservices. Prevents leaking secrets into spans and verifies collector error handling.
MIT ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing -a claude-codeWhat distributed-tracing does
The skill directs coding agents through instrumenting microservices with OpenTelemetry SDKs and OTLP exporters. It provides practical workflows for context propagation across HTTP boundaries and asynchronous queues, plus instructions to scrub credentials from span attributes.
This bundle does not install Jaeger or Tempo instances. You need an existing collector deployment or supported backend before configuring exporters, because the skill only handles instrumentation logic and failure verification.
What it helps with
- trace distributed operations across HTTP calls and message queues
- filter authorization credentials and sensitive payloads from span attributes
- verify that collector downtime does not disrupt incoming application traffic
- tune trace sampling rates according to observed queue loss
Example prompts for the agent
- Guide OpenTelemetry SDK and Jaeger integration for our microservices checkout flow
- Check context propagation across HTTP calls and message queue consumers
- Configure an OTLP exporter to ensure collector failures do not drop active requests
How to install distributed-tracing
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing -a claude-code2Manually: put the files in place
~/.claude/skills/distributed-tracing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/distributed-tracing/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing -a codex2Manually: put the files in place
.agents/skills/distributed-tracing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing -a cursor2Manually: put the files in place
.cursor/skills/distributed-tracing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/distributed-tracing2Manually: put the files in place
.github/skills/distributed-tracing/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/distributed-tracingManually: put the files in place
.devin/skills/distributed-tracing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about distributed-tracing
How to install distributed-tracing in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing -a claude-code. The skill file will be placed at ~/.claude/skills/distributed-tracing/SKILL.md.
What does distributed-tracing do?
It supplies an agent with workflows for OpenTelemetry instrumentation, Jaeger or Tempo integration, and context propagation rules across service boundaries.
Does distributed-tracing install a tracing backend?
No. It contains instructions and playbooks for client instrumentation, but requires an existing Jaeger, Tempo, or OpenTelemetry Collector setup.
Source text
SKILL.md · MIT
--- name: distributed-tracing description: "Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices." risk: critical source: community date_added: "2026-02-27" --- # Distributed Tracing ## When to Use Trace a request across services, diagnose latency and error propagation, or add observable boundaries to a new integration. ## Inputs and prerequisites Record installed SDK and backend versions, permitted collector endpoints, the service graph and a staging request. Inspect the installed version's primary documentation before selecting exporter APIs or deployment configuration. This bundle does not install a tracing backend. ## Procedure 1. Read `resources/implementation-playbook.md` and identify one user journey. 2. Configure the matching OpenTelemetry SDK and OTLP exporter before loading instrumented frameworks. Use `references/instrumentation.md` for propagation, shutdown and privacy checks. 3. Configure Jaeger using `references/jaeger-setup.md`, or the existing Tempo/collector deployment's supported configuration. Review listeners, authentication, transport protection, storage and retention before any deployment. 4. Propagate context over HTTP and asynchronous messages. Use stable operation names and allowlisted attributes. Do not log credentials, raw request bodies or sensitive query values. 5. Send successful and failing staging requests and verify connected spans in the backend. Record service identity, parentage, duration units and exporter errors. 6. Measure queue loss and overhead. Select sampling based on those observations; no fixed percentage guarantees coverage or performance. ## Example A checkout calls inventory and payment. Verify that the root request and both downstream operations share a trace, that a simulated payment timeout is recorded, and that no card data is present. Repeat with exporter connectivity unavailable: request handling must retain the application's defined behavior. ## Verification - Actual trace evidence for each exercised boundary, including queue consumers. - Allowed fields only; bounded attribute cardinality. - Shutdown flush and exporter failure behavior observed. - Access, storage and retention checked independently from UI availability. ## Limitations Head sampling can discard errors before tail sampling sees them. In-memory demos do not prove durable storage. Context propagation and cross-service clocks need actual integration tests; this guide is not a runnable multi-service application. ## Sources - [OpenTelemetry exporter documentation](https://opentelemetry.io/docs/languages/python/exporters/) — use the installed SDK's matching documentation.
© sickn33 · MIT · sickn33/agentic-awesome-skills
Similar skills
All skills for Backend and APIs →distributed-tracing by other authors comes first.