Tracing
Distributed Tracing
A trace is the set of spans that share one W3C trace_id. Parent/child links use parent_span_id. Missing spans stay missing.
Overview
Propagate W3C traceparent across services so each span lands with the same trace_id. Mydle stores what your collectors or SDKs send via OTLP — it does not synthesize a full mesh when only one service reports.
Identity
trace_id— authoritative distributed key (32 hex).span_id/parent_span_id— operation tree.- Optional
session_id, request /correlation_idfor joins to browser and logs.
Cross-service
Observed service names on spans build the waterfall and related edges. Service relationships in the product are from stored telemetry — not invented topology. See Service Relationships.
Limitations
- Never join traces on timestamps, latency similarity, or service name alone.
- Platform
mydle-web/mydle-workerspans are not customer graph nodes.