-
Notifications
You must be signed in to change notification settings - Fork 782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Exporting using gRPC doesn't work in net48 projects #6067
Comments
@rajkumar-rangaraj I did some investigation in to .NET Framework support awhile back. I did it in the context of removing the old gRPC library and supporting .NET Framework with the newer Grpc.Net.Client library. There are some notes in the description of this PR #4860. Now that the dependency for both gRPC libraries have been removed, maybe we can support .NET Framework with the |
A workaround of rolling back package OpenTelemetry.Exporter.OpenTelemetryProtocol to 1.10.0 resolves the issue whilst continuing to use all other packages on 1.11.0. |
Tried the workaround of using WinHttpHandler which supports HTTP/2 results in a System.Net.Http.HttpRequestException with BadRequest 400. Tried this with aspire as collector: I closed #6066 as it's the same bug. Small repro project can be found there. |
Adding a
I'm working on further to find the complete fix. |
Package
OpenTelemetry.Exporter.OpenTelemetryProtocol
Package Version
Runtime Version
net48
Description
I'm not able to export logs/metrics/traces using gRPC in net48 projects .
Steps to Reproduce
Expected Result
Traces get successfully exported
Actual Result
An exception is thrown at line 42 here
opentelemetry-dotnet/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/Implementation/ExportClient/OtlpGrpcExportClient.cs
Lines 35 to 45 in 75d947c
The exception message is
Only HTTP/1.0 and HTTP/1.1 version requests are currently supported. Parameter name: value
Additional Context
Exporting via HTTP works fine.
The text was updated successfully, but these errors were encountered: