Jon Christiansen

Has any progress been made on this front, or any additional plans formed?

I have one real-world case in hand at the moment, to provide a single way to provide the proper support for federated tracing properly both for projects who define and...

I've created a MR with an initial POC that exercises a very similar pattern to what I described above on how FederatedTracingInstrumentation would need to be signaled based on a...

Updated the MR completed the reactive version and added tests around it as well.

Created new implementation in new PR https://github.com/Netflix/dgs-framework/pull/1145 based on Instrumentation per PR feedback by @berngp in initial implementation proposal

https://github.com/Netflix/dgs/pull/106 created to supply corresponding documentation

@v3i1r4in -- Please let us know what maxSockets you change to, and also approximately how many unique host/port combos do you have across all of your subgraphs that your gateway...

Any chance this "FIXME: heavy-handed" mechanism of re-executing the query altogether [here in the POST-PROCESSING](https://github.com/apollographql/federation/blob/be02e6cc167d728558dee8388a2f2e9080c5bcec/gateway-js/src/executeQueryPlan.ts#L97-L103) could be exacerbating this issue as well?

Not their apm agent for node.js though, thats still OpenTrace based. It instruments almost everything else we want within our Node code, and is the agent supported at our company....

As of June 13, 2023 Datadog now provides (beta support) Otel span compatibility with their instrumentation library, thereby obsoleting this issue. https://github.com/DataDog/dd-trace-js/releases/tag/v4.2.0