Slf4j Fuent API and Logback TurboFilter

[Kiiv]

Hi,

I've opened a discussion in the slf4j github but perhaps it is more relevant here.

Logback offers to implement TurboFilters (https://logback.qos.ch/manual/filters.html#TurboFilter).

If I'm logging something with the old slf4j API just like :

   logger.error("error happened", new RuntimeException("Hi"));

then slf4j just call the error method of the underlying logger implementation.
With Logback it's something like :

    private void filterAndLog_2(final String localFQCN, final Marker marker, final Level level, final String msg,
            final Object param1, final Object param2, final Throwable t) {

        final FilterReply decision = loggerContext.getTurboFilterChainDecision_2(marker, this, level, msg, param1,
                param2, t);
        ...
    }

As you can see, the turboFilterChain is called with all the information passed to the method.

But if I'm logging something with the fluent API juste like :

logger.atError().setCause(new RuntimeException("Hi")).log("error happened");

then slf4j call the 'log' method of the underlying logger implementation.
This implementation completely bypass the TurboFilter chain.

The TurboFilter is still called when the "atError" method is called because the 'isErrorEnabled' method call it but at this step there is no information available about the message or exception to log.

Is there a way to use the new fluent API and have my TurboFilter work as intended ?

[ceki]

Related to LOGBACK-1719