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 >
