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
We just migrated away from honeycomb open telemetry library to the opentelemetry java implementation.
We started getting spammed with multiple connection related exceptions:
okhttp3.internal.http2.StreamResetException: stream was reset: NO_ERROR
java.net.SocketException: Broken pipe
Steps to reproduce
We started the service and the error logs are very frequent. We are using the library to export traces to Honeycomb using gRPC.
Expected behavior
No traces seem to be getting lost, however we get spammed with errors in the logs.
We just use Open Telemetry to export traces, it seems the server was rejecting logs and metrics. Disabling the export of those fixed our problem. Thanks!
Describe the bug
We just migrated away from honeycomb open telemetry library to the opentelemetry java implementation.
We started getting spammed with multiple connection related exceptions:
okhttp3.internal.http2.StreamResetException: stream was reset: NO_ERROR
java.net.SocketException: Broken pipe
Steps to reproduce
We started the service and the error logs are very frequent. We are using the library to export traces to Honeycomb using gRPC.
Expected behavior
No traces seem to be getting lost, however we get spammed with errors in the logs.
Actual behavior
There should be no errors in the logs.
Javaagent or library instrumentation version
v2.10.0
Environment
Docker image: eclipse-temurin:21-jre-alpine
Additional context
Some stack traces:
Cause:
The text was updated successfully, but these errors were encountered: