Correlation
Browser ↔ Traces
Browser errors and network events join traces when stored trace_id matches. Sessions join when public session_id matches on both sides.
Join rules
- Browser error / network → trace: equal
trace_id. - Browser session → trace: equal
session_id(s_…).
Propagation
Same-origin fetch/XHR: Browser SDK injects traceparent and X-Mydle-Session-ID. Backend continues the W3C trace and maps session into session.id on OTLP so traces.session_id is stored. Details: Trace Context.
Limitations
- No
traceparenton cross-origin / third-party by default. anonymousIdand internalbsess_*keys are not correlation ids.- Never join on URL, timing, or IP.