Proposed title of this feature request

Allow max_connection_duration_secs for config limit for vector socket sink

What is the nature and description of the request?

Improve overall efficiency and log delivery when fowarding logs to socket sink (syslog) behind a Load Balancer.

Why does the customer need this? (List the business requirements)
Persistent Connections:
When Vector opens a single TCP connection to a load balancer, the load balancer typically sticks to the same backend (syslog node) for the duration of that connection.

Uneven Distribution:
If all logs flow through a single connection, all data will be directed to the single syslog node the load balancer initially assigned the connection to, even if other syslog nodes are available. This creates an imbalance in log processing.
List any affected packages or components.

Red Hat OpenShift Logging

Vector Syslog (Socket Sink)

Additional Info:

This feature was requested in upstream some time back, below is the associated github:

 [-] https://github.com/vectordotdev/vector/issues/18488