You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the expected behavior?
Spans should be logged to the console, logged by the otel contribs collector, and logged to spans.json
What is the actual behavior?
Spans are not logged by the collector nor logged to spans.json when using API/SDK version 1.11.0.
Message in logs instead is: 2022-04-20T08:56:13.103-0400 warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:4317->127.0.0.1:50009: read: connection reset by peer {"grpc_log": true}
Additional context
When using API/SDK version 1.10.0 traces are being logged and exported properly
environment setup
3.9.5
0.48.0
Steps to reproduce
0.48.0
version of the OpenTelemetry Contribs Collector:What is the expected behavior?
Spans should be logged to the console, logged by the otel contribs collector, and logged to
spans.json
What is the actual behavior?
Spans are not logged by the collector nor logged to
spans.json
when using API/SDK version1.11.0
.Message in logs instead is:
2022-04-20T08:56:13.103-0400 warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:4317->127.0.0.1:50009: read: connection reset by peer {"grpc_log": true}
Additional context
When using API/SDK version
1.10.0
traces are being logged and exported properlyWhen using 1.11.0 console spans print but nothing is exported by the collector:
When using
main
branch:The text was updated successfully, but these errors were encountered: