OpenTelemetry Distributed Tracing & W3C TraceContext Propagation in Express.md
Telemetry & Observability

OpenTelemetry Distributed Tracing & W3C TraceContext Propagation in Express

Author: Robert BaindourovPublished: September 2, 2026Runtime: Node.js 26 & Linux Native

Debugging microservice latency spikes and database bottlenecks requires tracing request lifecycles across process boundaries. Implementing **OpenTelemetry (OTel)** with the W3C `traceparent` standard allows developers to follow a single website contact form submission from edge Nginx ingress to Node.js backend to MongoDB query execution in Grafana Tempo.

1. OpenTelemetry Span Hierarchy

Span NameComponent LayerCaptured Attributes
http.ingressNginx / ExpressHTTP method, route, tenant domain, client IP, response code.
mvc.controller.resolveNavigationServiceTenant lookup duration, cache hit/miss status.
db.mongo.queryMongoDB DriverCollection name, query filter, execution duration, document count.
react.ssr.renderReactDOMServerComponent name, HTML payload byte size, render latency.
Robert Baindourov

Written by Robert Baindourov — Systems Architect

Senior systems architect, full-stack engineer, and creator of the multiDomainCMS web platform. Specializing in high-throughput React SSR, zero-downtime blue/green infrastructure, and native Linux telemetry.