Have an option to enable TCP connection details in tracing.

[Samjin]

Is your feature request related to a problem? Please describe.

We'd like to be able to see what happened before POST /graphql span, how long it takes for TCP, DNS to establish the connection. This will be helpful to know if any optimization can be done for connection pool, keep alive sockets, dns cache etc.

In addition, it's even better if it could trace for non-subgraph TCP latencies as well because there could be quite some outgoing calls that's not going to subgraphs. E.g. Apollo reporting api. Often these APIs are overlooked with high latencies.

Describe the solution you'd like Have a option to turn the feature on so user can observe the details in trace and create monitors.

[abernix]

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

[Samjin]

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

Router to subgraphs