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
Right now the socket_listener input generates lots of noise due to health check probes. For example if you have a load balancer which opens a tcp socket to the input, and then closes the socket without writing anything (after completing SSL handshake), it generates 2 logs entries (in the case of SSL):
Apr 06 03:56:36 myhost telegraf[21963]: 2023-04-06T03:56:36Z E! [inputs.socket_listener] Error in plugin: connection not a TCP connection (*tls.Conn)
Apr 06 03:56:36 myhost telegraf[21963]: 2023-04-06T03:56:36Z E! [inputs.socket_listener] Error in plugin: creating decoder failed: write tcp 10.0.0.10:8085->10.0.2.9:33288: write: connection reset by peer
When you have many clients, this gets extremely noisy and make it hard to observe the logs for meaningful information.
Expected behavior
Silence
Actual behavior
Apr 06 03:56:36 myhost telegraf[21963]: 2023-04-06T03:56:36Z E! [inputs.socket_listener] Error in plugin: connection not a TCP connection (*tls.Conn)
Apr 06 03:56:36 myhost telegraf[21963]: 2023-04-06T03:56:36Z E! [inputs.socket_listener] Error in plugin: creating decoder failed: write tcp 10.0.0.10:8085->10.0.2.9:33288: write: connection reset by peer
Additional info
No response
The text was updated successfully, but these errors were encountered:
This suppresses several different logs that may be emitted when the connection is closed (locally or by remote) at various points.
Fixesinfluxdata#13043
This suppresses several different logs that may be emitted when the connection is closed (locally or by remote) at various points.
Fixesinfluxdata#13043
This suppresses several different logs that may be emitted when the connection is closed (locally or by remote) at various points.
Fixesinfluxdata#13043
Use Case
Right now the socket_listener input generates lots of noise due to health check probes. For example if you have a load balancer which opens a tcp socket to the input, and then closes the socket without writing anything (after completing SSL handshake), it generates 2 logs entries (in the case of SSL):
When you have many clients, this gets extremely noisy and make it hard to observe the logs for meaningful information.
Expected behavior
Silence
Actual behavior
Additional info
No response
The text was updated successfully, but these errors were encountered: