[feature request] Able to config GrpcChannel like HttpClient

[LeuisKen]

Package

OpenTelemetry.Exporter.OpenTelemetryProtocol

Is your feature request related to a problem?

We have a project based on .Net Framework 4.8 and grpc over HTTP (grpc-web). We want to build a custom collector based on the proto files with .net 8 and enable the grpc-web support. The OpenTelemetryProtocol package does not support it. I wonder if we can add an option like HttpClient for GrpcChannel.

Client code to support grpc-web is similar to this: https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/test/test-applications/integrations/TestApplication.GrpcNetClient/Program.cs#L51

Here I created a repo to reproduce the issue: https://github.com/LeuisKen/OTLPGrpcWeb

If you start the OTLPGrpcService, which listens to http://localhost:4317, and run the OTLPConsoleApp console app, no logs are sent to the service.

Here is the error inside the response:

Status(StatusCode="Unavailable", Detail="failed to connect to all addresses", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1729793704.966000000","description":"Failed to pick subchannel","file":"..\..\..\src\core\ext\filters\client_channel\client_channel.cc","file_line":3129,"referenced_errors":[{"created":"@1729793704.966000000","description":"failed to connect to all addresses","file":"..\..\..\src\core\lib\transport\error_utils.cc","file_line":163,"grpc_status":14}]}")

What is the expected behavior?

Add a new GrpcChannel option like the HttpClient option we have. Then we can customize the behavior of Grpc channel, no matter we are using HttpHandler or WinHttpHandler.

Which alternative solutions or features have you considered?

Not yet.

Additional context

If you like the proposal, I'll be glad to create a PR to implement it.

[rajkumar-rangaraj]

Starting from version 1.11.0-rc.1 of OpenTelemetry.Exporter.OpenTelemetryProtocol, you will be able to use HttpClient for gRPC as well.