Revision history [back]

One solution is to use Logback's filtering capabilities to exclude the specific type of Exception from being logged. This can be done by creating a custom filter that checks the type of the Exception and returns a decision to either include or exclude it from the log. The filter can then be added to the Logger or Appender configuration to ensure that the excluded Exception is not logged.

Here is an example of how to create the custom filter:

import ch.qos.logback.classic.spi.ILoggingEvent;
import ch.qos.logback.core.filter.AbstractMatcherFilter;

public class CustomExceptionFilter extends AbstractMatcherFilter<ILoggingEvent> {

    @Override
    public FilterReply decide(ILoggingEvent event) {
        if (event.getThrowableProxy() != null && event.getThrowableProxy().getClassName()
                .equals("com.example.ExcludedException")) {
            return FilterReply.DENY; // exclude the Exception from log
        }
        return FilterReply.ACCEPT; // include all other events in log
    }
}

In this example, the filter checks if the event has a ThrowableProxy (i.e., an Exception) and if its class name is "com.example.ExcludedException". If it is, the filter returns FilterReply.DENY to exclude the event from the log. If not, it returns FilterReply.ACCEPT to include the event in the log.

To use this filter in Logback configuration, add the following to the <appender> or <logger> section:

<filter class="com.example.CustomExceptionFilter" />

This will apply the custom filter to the Appender or Logger and exclude the specified Exception from being logged.