W3C Trace propagation via ReverseProxy

[chandramouleswaran]

What should we add or change to make your life better?

To start off - this project is awesome. I have been experimenting with this and GRPC bi-directional streaming works like a charm. For our use case, we would like to get the distributed traces emitted correctly. Today, ASP .NET Core + HttpClient make this happen seamlessly.

I think the problem is the client factory is using SocketsHttpHandler and it does not support passing trace context automatically.
dotnet/runtime#31261

Instead, if this changes to HttpClientHandler - we would end up getting the headers injected to visualize an E2E trace via the Reverse proxy. (May be - I am not very familiar with the code but this was the one which stood out)

Why is this important to you?

This is important for cases where we have to understand the calling pattern across multiple microservices in our environment.

Please let me know if this is a good idea to try out - if so, I can help out with the PR to make this change as well.

[Tratcher]

Yeah, we'll get this sorted out either as part of #137, or by directly fixing dotnet/runtime#31261.

[samsp-msft]

Duplicate of #292