Minimal type-safe context propagation container
-
Updated
Nov 18, 2026 - Swift
Minimal type-safe context propagation container
W3C Trace Context for Laravel: one id follows a request through its logs, its queued jobs and the services it calls.
W3C Trace Context purpose of and what kind of problem it came to solve.
Vendor-neutral OpenTelemetry tracing for A2A agents and MCP services, with W3C context propagation and privacy-safe telemetry.
Two local HTTP services and a real OpenTelemetry Collector demonstrate trace parentage, request-context isolation and baggage allowlisting. A headless verifier checks exported OTLP evidence instead of requiring a tracing dashboard.
Apollo Link that applies Trace Context headers to your Apollo Client requests.
Walks a graph of your services and makes real, repeat-safe HTTP GET/HEAD and gRPC health calls with W3C trace context. Exports its own spans over OTLP. Apache-2.0.
Structured logging with trace propagation, PII masking, and error classification — the log contract as code. Zero dependencies, TypeScript, Node 20+.
'traceheader' based trace context propagation for express 4
W3C Trace Context propagation runtime for Coretsia: bounded traceparent extraction and injection, deterministic validation, and noop fallback.
OpenTelemetry helpers for Go: spans, trace-context propagation, and optional OTLP/HTTP setup with an API-only core.
To associate your repository with the trace-context topic, visit your repo's landing page and select "manage topics."