Verified:GitHub

distributed-tracing

Instrument services with OpenTelemetry and propagate traces across microservice boundaries.

Updated Mar 29, 2026

Search Tags:#observability #instrumentation #opentelemetry #distributed-tracing #trace-propagation #trace-sampling #logs-trace-correlation

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill distributed-tracing-marquesfelip

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: distributed-tracing
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/distributed-tracing
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill distributed-tracing-marquesfelip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distributed tracing enables end-to-end visibility across multiple services, helping teams diagnose latency, bottlenecks, and dependency issues by correlating requests across service boundaries.

Core Features & Use Cases

Automatic instrumentation with OpenTelemetry across HTTP, gRPC, and queues, producing shared trace contexts.
Manual span creation for business logic with stable naming and semantic conventions.
Trace visualization and correlation with logs and metrics to identify slow services and bottlenecks.

Quick Start

Initialize OpenTelemetry in each service and ensure all HTTP/gRPC calls propagate trace context to the centralized collector.

Frequently Asked Questions about distributed-tracing

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

FAQPage Schema

How do I propagate distributed traces across microservice boundaries?▼

Distributed traces are propagated across microservice boundaries by initializing the OpenTelemetry SDK and ensuring HTTP, gRPC, and queue calls automatically forward the shared trace context to a centralized collector for end-to-end visibility.

What is distributed tracing used for in microservice architectures?▼

Distributed tracing is used to diagnose latency bottlenecks and map dependencies by correlating requests across service boundaries, enabling teams to visualize slow services and correlate traces with logs and metrics for performance analysis.

How do I set up OpenTelemetry automatic instrumentation for HTTP and gRPC?▼

OpenTelemetry automatic instrumentation is set up by initializing the SDK in each service with proper resource attributes like service.name and deployment.environment, which automatically produces shared trace contexts for HTTP, gRPC, and queues.

Does distributed tracing work with serverless components and message queues?▼

Distributed tracing works with serverless components and message queues by applying OpenTelemetry automatic instrumentation to propagate trace context across these boundaries, ensuring cross-service correlation and dependency mapping.

Why do I need resource attributes like service.name for trace correlation?▼

Resource attributes like service.name, service.version, and deployment.environment are required for trace correlation because they provide the necessary contextual metadata to identify and group spans correctly within the centralized OTEL collector backend.

Can I create manual spans for business logic alongside automatic instrumentation?▼

Manual spans can be created for business logic alongside automatic instrumentation by using stable naming and semantic conventions, allowing precise tracking of specific operations within the broader distributed trace context.