ERROR o.f.logger.sender.RawSocketSender - org.fluentd.logger.sender.RawSocketSender java.net.SocketException: Connection timed out (Write failed)

[Einsteinl]

In my use case, we can not assume that fluentd will always be running. Ideally, the logger would log as usual if fluentd is running; if it is not running, it should probably log a warning and move on instead of throwing exceptions; finally, it should silently try to reconnect in the background and resume logging as soon as a connection is available.

Ideally the library would also do some in-memory buffering to minimize loss of log msgs. Thoughts?

[sndyuk]

@Einsteinl Yes, it should be so. I'll check it.

[sndyuk]

@Einsteinl You can use fluency for the time being which has the retry feature. fluentd-logger doesn't have the retry feature but the feature must be needed on logback-more-appenders. I will implement it when I have time.