distributed-tracing-specialist

Enable OpenTelemetry distributed tracing with Jaeger for HuleEdu services.

Updated Aug 27, 2026

Search Tags:#middleware #opentelemetry #HTTP #distributed tracing #jaeger #correlation #trace context

Ready to run

npx skills add https://github.com/paunchygent/docforge --skill distributed-tracing-specialist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: distributed-tracing-specialist
Source: https://github.com/paunchygent/docforge/tree/main/frontend/.claude/skills/distributed-tracing
Command: npx skills add https://github.com/paunchygent/docforge --skill distributed-tracing-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable OpenTelemetry distributed tracing with Jaeger in HuleEdu services. This Skill covers tracer initialization, span creation, W3C trace context propagation, and correlating traces with logs and metrics.

Core Features & Use Cases

Tracer Initialization and Span Creation
Trace Context Propagation across HTTP, Kafka, and queues
Middleware Integration for automatic HTTP tracing
Correlation with logs and metrics
Context7 integration for latest documentation

Quick Start

Initialize the tracer with init_tracing("my-service"), set up tracing middleware, and start instrumenting operations; view traces in Jaeger UI.

Frequently Asked Questions about distributed-tracing-specialist

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

FAQPage Schema

How do I set up distributed tracing across microservices?▼

Distributed tracing provides end-to-end visibility into request flows across services. Initialize OpenTelemetry with a tracer, create spans for operations, propagate trace context via W3C headers over HTTP and Kafka, and correlate traces with logs and metrics in Jaeger for operational insight.

How do I propagate trace context over HTTP requests?▼

W3C Trace Context propagation embeds trace identifiers into HTTP headers, enabling spans across service boundaries. Extract context from incoming requests, inject it into outgoing calls, and use middleware to automate this process for all HTTP framework operations.

Can I use OpenTelemetry with Kafka message queues?▼

Yes. OpenTelemetry supports trace context propagation over Kafka by extracting and injecting context into message headers, allowing traces to flow through async queue operations and maintaining correlation across producer and consumer spans.

What's the best way to correlate distributed traces with logs and metrics?▼

Embed trace IDs from OpenTelemetry spans into log output and metric attributes, creating a unified observability signal. Jaeger links these signals together, enabling drill-down from traces to logs and metrics for complete operational context.

How do I instrument HTTP frameworks for automatic tracing?▼

Middleware integration captures HTTP requests and responses as spans automatically without manual instrumentation. Configure tracing middleware in your HTTP framework to record span data, record errors, and propagate context without code changes per endpoint.

When should I use manual span creation versus automatic instrumentation?▼

Automatic middleware captures HTTP layer spans; manual spans instrument business logic, database queries, or custom operations. Combine both: let middleware handle HTTP, then create explicit spans for domain-specific work to maintain trace granularity.