Open
Description
I'm currently operating Logstash servers with a TCP input. In front of Logstash, there is a DNS configured for round-robin distribution of connections to Logstash.
Some of my clients write data via a single instance of Logstash using the TCP output plugin. However, since the current output tcp configuration lacks a load balancing feature, the Logstash instance handling the client's connection is under strain.

- only the top yellow line is receiving the logstash client(w/ tcp output plugin) request
If the Logstash TCP output plugin could support a 'loadbalance' option, similar to Beats, I believe our Logstash(server) instances would not face these difficulties.
I've drawn a figure to help illustrate the current state and the desired features for better understanding.
Do you think implementing such a feature is possible?