Hello Ihsiak , TurboFilters are added to the logger context. In other words, they are global to the logging environment. Place the <turboFilter> element as a child of <configuration> and *not* as a child of <appender>. HTH, Ihsiak wrote:

Hello everybody I am trying to configure additional appender that would log only messages marked with specified Marker. Unfortunately when I put <turboFilter> block inside appender definition (in logback.xml file) I keep getting following errors:

12:27:48,312 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@5:66 - no applicable action for [turboFilter], current pattern is [[configuration][appender][turboFilter]] 12:27:48,312 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@6:11 - no applicable action for [marker], current pattern is [[configuration][appender][turboFilter][marker]] 12:27:48,312 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@7:15 - no applicable action for [onMismatch], current pattern is [[configuration][appender][turboFilter][onMismatch]] 12:27:48,312 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@8:12 - no applicable action for [OnMatch], current pattern is [[configuration][appender][turboFilter][OnMatch]]

There's no such problem if I put <turboFilter> inside root <configuration> block (except that it doesn't do the job then).

are turbo filters available only at root level (should I use evaluator filter instead)?

related jars in the classpath: - logback-classic-0.9.16.jar - logback-core-0.9.16.jar - slpf4j-api.1.5.8.jar

-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch