Hi Pavel, One alternative would be to create a logger with a different name and assign it DEBUG or INFO as a level.
-- Ceki Gülcü Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch On 1/17/2023 4:35 PM, Pavel Ilmenkov wrote: > Hello, > > I'm trying to use the proposed approach for the nested appenders > removing from SiftingAppender as: > ----------------------------- > // will cause the nested appender reach end-of-life. It will > // linger for a few seconds. > logger.info <http://logger.info>(FINALIZE_SESSION_MARKER, "About to > end the job"); > ----------------------------- > > But I'm not sure how to get the proper logger level to use in the above > example. > For example in case of log level set to ERROR in logback settings xml > file, the logger.info <http://logger.info>(FINALIZE_SESSION_MARKER) does > not do the job. > > I did not find any easy way to be sure to call a logger with > FINALIZE_SESSION_MARKER except using logger.error() which does not look > good. > > Could you please help me to find if I'm missing something? > > Thanks, > Pavel _______________________________________________ logback-user mailing list logback-user@qos.ch https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-user
