Logstash shuts down if gelf output TCP connection is refused

Elastic Stack Logstash
#1

I have configured logstash with a TCP gelf output. However, if the TCP connection cannot be established (e.g graylog is down or hasn't yet been configured to listen on the port), the pipeline aborts and logstash shuts down.
Is that the expected behaviour? Should it not be retrying to connect rather than going down and requiring manual intervention?

Thanks

#2

Unfortunately yes. If it is able to connect at startup and gelf restarts I do not think it will recover from that either. Using UDP rather than TCP avoids these issues but brings a whole other set of problems (security, reliability etc.)

#3

Thanks for the confirmation. Would an enhancement be possible to retry to connect every X seconds?

#4

It could be done, but I do not see anyone volunteering to do it.