Jesse Rosenberger

@awdng Could you provide information about what version of the Router you're using?

@bnjjj Should this have been marked as one of the "Fixes" in #5022? (In other words, can it be closed?)

The router would only originate a trace Id when it doesn't get one from the headers. Do you have tracing [propagation](https://www.apollographql.com/docs/router/configuration/telemetry/exporters/tracing/overview/#propagation) setup or any exporters enabled? Can you share more...

Put another way, the thing you're asking for should definitely already work. The router is meant to play nice with existing distributed tracing headers, including passing them to subgraphs as...

What is your subgraph server implemented in and what telemetry mechanism (SDK, format, etc.) are you using in it?

Should we close #1840 since its ideas have been folded into the above?

Given what you've written here, this should certainly be working. Have you tried any variations of casing (e.g., all lower-case), to see if that helps? I'll mark this as a...

Are you talking about the connectivity between the client and the router or the router and the subgraphs?

I've opened up https://github.com/apollographql/router/pull/5029 to land this on 1.45.1. I'll also note that we've introduced https://github.com/apollographql/router/pull/5031 and https://github.com/apollographql/router/pull/5030 to remove the "proto has changed? here, have a failing dev branch...

For whatever reason, this landed cleanly and passed CI on https://github.com/apollographql/router/pull/5029 — which targeted `1.45.1`, whereas tests are refusing to pass on this PR. I'm unable to tell why.