Closed breml closed 2 years ago
For reconnects Stud::try is used (https://github.com/logstash-plugins/logstash-output-tcp/blob/master/lib/logstash/outputs/tcp.rb#L123), which has two side effects:
Stud::try
reconnect_interval
Just wondering if there was any consideration given to this; Stud:try preventing reconnect_intervalfrom having an affect seems like a bug to me?
Stud:try
For reconnects
Stud::try
is used (https://github.com/logstash-plugins/logstash-output-tcp/blob/master/lib/logstash/outputs/tcp.rb#L123), which has two side effects:Stud::try
does not respect thereconnect_interval
configured for the plugin but its own intervals, defined in https://github.com/jordansissel/ruby-stud/blob/master/lib/stud/try.rb#L26Stud::try
does not log to the Logstash log file but to stdout, which makes problem finding very difficult, if logstash is executed as a service.