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
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T340551 distributed tracing epic | |||
| Open | None | T320549 distributed tracing v0 [minimum viable] | |||
| Open | None | T320556 Micro-specification for how service owners should propagate tracing headers | |||
| Resolved | pmiazga | T320559 Trace header propagation for MediaWiki | |||
| Resolved | pmiazga | T344926 Propagate x-request-id header from MultiHttpClient in MediaWiki (e.g. SessionStore) | |||
| Resolved | pmiazga | T345295 MultiHttpClient should handle headers from __construct | |||
| Open | None | T320561 Trace header propagation for service-template-node and all service-runner services | |||
| Open | None | T344148 Trace header propagation for Proton service | |||
| Resolved | pmiazga | T346209 Send tracing headers from Shellbox client |
Event Timeline
Comment Actions
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.