Current Error Handling does not return false on logging errors

[fluent]

Current Error Handling does not return false on logging errors

[repeatedly]

How about using fluency instead of fluent-logger-java?
We are now considering replacing fluent-logger-java with fluency.

[komamitsu]

@obokaiwele

1

You can set an ErrorHandler if you want to do something other than just logging like

        FluentLogger logger = FluentLogger.getLogger(null);
        logger.setErrorHandler(new ErrorHandler() {
            @Override
            public void handleNetworkError(IOException ex)
            {
                // Notify me via email or something
            }
        });

As for the return value of log(), it returns true if it can store an event in memory since fluent-logger is going to retry to send the buffered event later.

2

I guess fluent-logger didn't notice the buffer full of the Fluentd.

in_forward/out_forward plugins of Fluentd support ACK response http://docs.fluentd.org/v0.12/articles/out_forward#requireackresponse. Without this feature, clients of in_forward plugin can't notice the failures of sending to in_forward plugin.

Unfortunately, fluent-logger doesn't support the feature and there is no plan to support it for now. But Fluency, which is yet another fluent logger, supports it https://github.com/komamitsu/fluency#enable-ack-response-mode. On the other hand, Fluency doesn't support custom error handler, but I'll implement the feature later.

[komamitsu]

Unfortunately, fluent-logger doesn't support the feature and there is no plan to support it for now. But Fluency, which is yet another fluent logger, supports it https://github.com/komamitsu/fluency#enable-ack-response-mode. On the other hand, Fluency doesn't support custom error handler, but I'll implement the feature later.

Fluency 1.4.0 now supports custom error handler and user can know and handle a send error.