Logback's documentation on how all the different config files get used isn't very detailed but this is what I have found,
* Storm sets -Dlogback.configurationFile option for all of its workers * Logback seems to only want 1 config file and picks the one set by the property first ( https://github.com/qos-ch/logback/blob/v_1.1.1/logback-classic/src/main/java/ch/qos/logback/classic/util/ContextInitializer.java#L118-L136 ) This seems to imply that the storm logback/cluster.xml is the only way to configure logging settings which also effects the whole cluster or a specific supervisor if you do it manually. On Fri Nov 07 2014 at 10:21:02 AM John Reilly <[email protected]> wrote: > You do not need to create a logback.xml. You should use the config that > is included as part of storm. $STORM_DIR/logback/cluster.xml > > On Fri Nov 07 2014 at 7:04:05 AM Bryan Baugher <[email protected]> wrote: > >> I do see logs the problem is I am trying to increase the log levels from >> INFO to WARN for a number of packages but still see the INFO messages after >> deploying the new jar. I used the log4j -> logback translator to create my >> logback.xml file. >> >> On Thu Nov 06 2014 at 5:43:44 PM John Reilly <[email protected]> >> wrote: >> >>> You said that log levels are not being honored, but it is not clear to >>> me if this means that you are seeing some logs, but just not seeing finer >>> grained logs, e.g. DEBUG, or does it mean that you are not seeing any of >>> the logs that you are expecting to see. >>> >>> If you are not seeing any logs, it might be a binding problem. >>> >>> If I remember correctly, the only libs that you should include in any >>> build are the slf4j-api and logback-classic since the logback lib contains >>> the binding. If you include any other bindings, you will run into >>> problems. Examples of other bindings are *slf4j-log4j12-1.7.7.jar, etc.* >>> >>> Also, log4j-over-slf4j is only relevant if you have any code that is >>> logging to log4j directly. It is not harmful to include it anyway if you >>> are not sure. >>> >>> Cheers, >>> John >>> >>> >>> On Thu Nov 06 2014 at 1:29:21 PM Bryan Baugher <[email protected]> wrote: >>> >>>> Hi everyone, >>>> >>>> We recently switched to Storm 0.9.2 which moved to logback. We use the >>>> slf4j API and provide a log4j.properties in our topology jar but noticed >>>> the log levels set in the log4j.properties were not being honored. I read >>>> in the doc for log4j-over-slf4j[1] that 'Note that as a result of this >>>> migration, log4j configuration files will no longer be picked up.' So >>>> I converted my log4j.properties to logback.xml and re-deployed the topology >>>> but the log levels still don't seem to be honored. Does anyone have any >>>> suggestions on things I should try? >>>> >>>> [1] - http://www.slf4j.org/legacy.html >>>> >>>
