This message was deleted.
s
Slackbot
01/03/2023, 2:29 PMThis message was deleted.
s
Srikanth Chekuri
01/03/2023, 2:53 PMPlease share the full log message
p
Pranay
01/03/2023, 4:12 PM
@Chintan Patel 👆
c
Chintan Patel
01/03/2023, 4:16 PM@Srikanth Chekuri - Above is full error log message we are observing.
s
Srikanth Chekuri
01/03/2023, 4:27 PMSorry, I was asking for the full log output for the collector.
c
Chintan Patel
01/04/2023, 1:26 PMPlease 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}
p
Pranay
01/04/2023, 1:41 PM
@Srikanth Chekuri 👆
s
Srikanth Chekuri
01/04/2023, 2:58 PMThis is probably some networking issue. How much data are you sending?
c
Chintan Patel
01/04/2023, 3:58 PMThat I need to check.
88 Views
SigNoz Community
SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.
Powered by