# Distributed Tracing Context Propagation

> W3C Trace Context propagation across service boundaries for distributed tracing. PROACTIVELY activate for: (1) Implementing trace context propagation, (2) Cross-service correlation, (3) Setting up traceparent headers, (4) Baggage propagation, (5) Multi-service debugging. Triggers: "distributed tracing", "trace context", "traceparent", "correlation", "span", "baggage", "propagation"

- Skill: `agentient/distributed-tracing-context-propagation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add agentient/distributed-tracing-context-propagation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/agentient/distributed-tracing-context-propagation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Agentient (https://skillmd.com/u/agentient)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/agentient/distributed-tracing-context-propagation

---


# Distributed Tracing Context Propagation

This skill provides expertise in distributed tracing and context propagation across microservices.

## Overview

Distributed tracing enables tracking requests as they flow through multiple services, making it possible to understand system behavior and diagnose issues in microservice architectures.

## Key Concepts

- **W3C Trace Context**: Standard for trace context propagation (traceparent, tracestate)
- **Span**: A single operation within a trace
- **Trace ID**: Unique identifier for an entire request flow
- **Span ID**: Unique identifier for a specific operation
- **Baggage**: Key-value pairs propagated across service boundaries

## Implementation Patterns

### HTTP Header Propagation

```
traceparent: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01
tracestate: vendor1=value1,vendor2=value2
```

### Context Extraction and Injection

1. Extract context from incoming request headers
2. Create child spans for local operations
3. Inject context into outgoing request headers

## Best Practices

1. Always propagate trace context across service boundaries
2. Use baggage for cross-cutting concerns (user ID, tenant ID)
3. Correlate logs with trace IDs
4. Set appropriate sampling rates

[Content to be expanded based on plugin_spec_agentient-observability.md specifications]