sickn33/agentic-awesome-skills / plugins/aasb-aas-observability-ir/skills/distributed-tracing
distributed-tracing
VerifiedImplement distributed tracing with Jaeger and Tempo for request flow visibility across microservices.
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
- Read
resources/implementation-playbook.mdand identify one user journey. - Configure the matching OpenTelemetry SDK and OTLP exporter before loading instrumented frameworks. Use
references/instrumentation.mdfor propagation, shutdown and privacy checks. - 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. - 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.
- Send successful and failing staging requests and verify connected spans in the backend. Record service identity, parentage, duration units and exporter errors.
- 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 — use the installed SDK's matching documentation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |