Hello Support team - We are observing below timeout error from the otelcollector. Can someone please help to resolve this error? [otel.javaagent 2023-01-03 141902:966 +0000] [OkHttp http://otelcollector.duclo.net:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: timeout [otel.javaagent 2023-01-03 142002:959 +0000] [OkHttp http://otelcollector.duclo.net:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: timeout [otel.javaagent 2023-01-03 142102:958 +0000] [OkHttp http://otelcollector.duclo.net:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: timeout

Please share the full log message

@Chintan Patel 👆

@Srikanth Chekuri - Above is full error log message we are observing.

Sorry, I was asking for the full log output for the collector.

Please see below logs from the collector pod. 2023-01-04T090126.785Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.11.954630: read: connection timed out {"grpc_log": true} 2023-01-04T091957.828Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.11.928216: read: connection timed out {"grpc_log": true} 2023-01-04T093538.112Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.11.933195: read: connection timed out {"grpc_log": true} 2023-01-04T093636.992Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.11.92585: read: connection timed out {"grpc_log": true} 2023-01-04T094058.112Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.11.93940: read: connection timed out {"grpc_log": true} 2023-01-04T094312.512Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.11.91675: read: connection timed out {"grpc_log": true} 2023-01-04T094725.696Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.11.921781: read: connection timed out {"grpc_log": true} 2023-01-04T095607.680Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.11.91806: read: connection timed out {"grpc_log": true} 2023-01-04T100757.568Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.11.95218: read: connection timed out {"grpc_log": true} 2023-01-04T103018.752Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 172.16.29.1014317 >172.16.30.7346755: read: connection timed out {"grpc_log": true}

@Srikanth Chekuri 👆

This is probably some networking issue. How much data are you sending?

That I need to check.