FluentLogger should do best effort logging

[diwakergupta]

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?

[komamitsu]

Thanks for your interest in fluent-logger-java.

FluentLogger in current implementation buffers messages in memory when it fails to send. Also, it tries to reconnect and resend the buffered messages when FluentLogger#log() called after the disconnection.

[komamitsu]

@diwakergupta If you have a further question, please reopen this issue and feel free to ask us. Thanks!