Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sickn33/agentic-awesome-skills --skill distributed-tracing -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/distributed-tracing/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/distributed-tracing/

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.

distributed-tracing Seth Hobson This skill sets up distributed tracing with Jaeger and Tempo. Use it to inspect request paths and find latency or failure points across microservices. CX Codex +1 10,700installs observability-guidelines Mindrally observability-guidelines guides coding agents on implementing OpenTelemetry tracing, metrics collection, and JSON logging across distributed microservices. CX Codex +1 826installs 183-java-observability-tracing-opentelemetry Juan Antonio Breña Moral 183-java-observability-tracing-opentelemetry guides OpenTelemetry distributed tracing setup in Java services with context propagation and semantic attributes. CX Codex +1 253installs distributed-debugging Seth Hobson distributed-debugging — a plugin for tracing and debugging distributed systems: it helps you see what happens between microservices. CX Codex ★ 42,780repo stars agentlens-tracing-instrument wandb agentlens-tracing-instrument — a skill for Claude Code and Cursor adds Forge AgentLens tracing to Python or TypeScript agents. Runs when asked to trace agent turns, model calls, tools, or subagents. CX Codex +1 200installs langchain-agent-tracing langchain-ai langchain-agent-tracing is a Claude Code skill for setting up LangSmith tracing in agents and LLM apps. It helps with instrumentation, destinations, and trace organization. CX Codex +1 298installs tempo grafana tempo is a Claude Code skill for deploying Grafana Tempo and writing TraceQL queries. It helps with tracing setup, slow-request searches, and cases where Explore shows no traces. CX Codex +1 5,300installs

From the same set187

The whole set →
varlock-claude-skill The varlock-claude-skill skill adds explicit checks for environment variables and secret exposure across Claude sessions, terminals, logs, and Git commits. CX Codex +1 ★ 50,109repo stars secrets-management secrets-management — a skill that walks an agent through secret handling in CI/CD: picking a backend, scoping access, rotating credentials and proving values never reach logs or artifacts. CX Codex +1 ★ 50,109repo stars security-scanning-security-sast security-scanning-security-sast — a skill for static code analysis (SAST) that detects vulnerabilities, hardcoded secrets, and security policy violations across multiple languages and frameworks. CX Codex +1 ★ 50,109repo stars distributed-debugging-debug-trace distributed-debugging-debug-trace sets up debugging and distributed tracing: trace boundaries, key spans, correlation IDs, and a check that traces actually cover the request path. CX Codex +1 ★ 50,109repo stars observability-monitoring-slo-implement observability-monitoring-slo-implement is a Claude Code skill for defining SLI and SLO targets, setting error budgets, and planning reliability monitoring tied to product priorities. CX Codex +1 ★ 50,109repo stars create-pr create-pr is a skill for Claude Code and other agents that redirects pull request drafting and editing requests to the canonical pr-writer workflow. CX Codex +1 ★ 50,109repo stars observability-monitoring-monitor-setup observability-monitoring-monitor-setup — a skill that walks your agent through planning metrics, distributed tracing, log aggregation and dashboards for an app and the infrastructure under it. CX Codex +1 ★ 50,109repo stars analytics-tracking Designs and audits analytics tracking setups so metrics reflect genuine user intent instead of junk clicks. Useful when building event taxonomies or auditing GA4 and GTM. CX Codex +1 ★ 50,109repo stars

Project sponsors

Companies that keep this analytics open