distributed-tracing

Design OpenTelemetry-first distributed tracing with span naming, propagation, and sampling policies.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/jamesogunsan/prod-eng-skills --skill distributed-tracing-jamesogunsan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributed-tracing
Source: https://github.com/jamesogunsan/prod-eng-skills/tree/main/plugins/observability/skills/distributed-tracing
Command: npx skills add https://github.com/jamesogunsan/prod-eng-skills --skill distributed-tracing-jamesogunsan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Distributed tracing helps teams diagnose cross-service requests, but many projects struggle with a clear strategy for instrumentation, propagation, and sampling. This Skill guides the rollout and evaluation of traces to improve visibility, debugging efficiency, and diagnostic confidence.

Core Features & Use Cases

  • OpenTelemetry-first instrumentation across services, message queues, and background jobs
  • Consistent span naming, meaningful attributes, and robust context propagation
  • Trace-based diagnostics with logs, metrics, and deployment context for rollout planning

Quick Start

Deploy OpenTelemetry instrumentation to a sample service and validate end-to-end trace propagation.

Frequently Asked Questions about distributed-tracing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement distributed tracing with OpenTelemetry across microservices?

Distributed tracing with OpenTelemetry requires consistent span naming, meaningful attributes, and robust context propagation across services to achieve end-to-end trace visibility for cross-service requests.

What is the best way to propagate trace context through message queues and background jobs?

Trace propagation through message queues and background jobs requires OpenTelemetry-first instrumentation that maintains consistent context across asynchronous boundaries to ensure continuous trace correlation.

How do I configure sampling policies for distributed tracing?

Sampling policies for distributed tracing dictate which traces get recorded, requiring careful configuration to balance diagnostic visibility with storage costs during instrumentation rollout and trace-quality reviews.

Can I correlate distributed traces with logs and metrics?

Correlating distributed traces with logs and metrics enables trace-based diagnostics by attaching deployment context and trace IDs to log entries for comprehensive cross-service request analysis.

When do I need distributed tracing for my microservices architecture?

Distributed tracing is needed when diagnosing cross-service requests in microservices architectures, providing visibility into request paths, latency bottlenecks, and debugging efficiency for complex service interactions.

How do I validate end-to-end trace propagation across services?

Validating end-to-end trace propagation involves deploying OpenTelemetry instrumentation to a sample service and verifying that span context transfers correctly across service boundaries for complete trace visibility.