Observability
Correlation
Mydle joins browser, traces, and logs only when the same stored identifier exists on both sides. Time windows, service names, and message similarity never create a DIRECT relationship.
Principle
Correlation is reference lookup, not inference. If an ID is missing on either side, the product shows no edge — it does not invent joins from timestamps.
Keys
trace_id— authoritative distributed key (W3C).span_id— operation identity.session_id— public browser session correlation id (s_…).request_id— optional HTTP / request identity.correlation_id— request-level identity (maps with request identity in stores that use this name).
Do not collapse session_id, request_id, or span_id into trace_id.
API
GET /api/app/correlation?type=trace|span|session|request&id=… — session auth. Returns DIRECT references (trace, spans, logs, browser, session) or empty when nothing matches. Optional project filter.
Limitations
- No probabilistic or time-window joins.
- Platform OTel / Trigger jobs are not part of the customer correlation graph.
anonymousIdis visitor uniqueness for RUM — not a join key to traces or logs.