Page MenuHomePhabricator

Micro-specification for how service owners should propagate tracing headers
Open, Needs TriagePublic


longer writeup to-do, but, tldr: it's perhaps undesirable to (at least initially) force lots of things to depend on the OpenTelemetry libraries just for context propagation, when we could instead have a list of headers to copy from incoming requests (if present) to outgoing sub-requests

Event Timeline

Would also like some guidance for how to pass on this info in emitted data events. We already produce the request_id, but perhaps we can make a more standardized tracing schema fragment for this.