If you want to adjust on a per topology basis create a logback config and package in uber jar
The config should be an included logback config file rather than stand alone, so root tag is <included> After that all storm cluster.xml files should be updated to include <include optional="true" resource="logback_include.xml"/> From: Lin Zhao [mailto:[email protected]] Sent: 21 April 2014 18:10 To: [email protected] Subject: Re: Logging levels You should probably add a new logger and appender for your topology such that it doesn't include storm's infrastructure logging. e. g. <appender name="A1" class="ch.qos.logback.core.FileAppender"> <file>myApp.log</file> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss} %c{1} [%p] %m%n</pattern> </encoder> </appender> <logger name="com.my.awesome.topology" level="INFO"> <appender-ref ref="A1"/> </logger> On Mon, Apr 21, 2014 at 9:42 AM, Software Dev <[email protected]<mailto:[email protected]>> wrote: Is there any way to adjust this per topology or project as opposed to system wide? On Sun, Apr 20, 2014 at 11:23 PM, 朱春来 <[email protected]<mailto:[email protected]>> wrote: > Try to modify the property file of log4j which is in the $STROM_HOME/log4j > > > 2014-04-19 6:59 GMT+08:00 Software Dev > <[email protected]<mailto:[email protected]>>: > >> How can one change the log levels.. the output is insane! > > > > > -- > Thanks, > > Chunlai -- Lin Zhao https://wiki.groupondev.com/Message_Bus<https://urldefense.proofpoint.com/v1/url?u=https://wiki.groupondev.com/Message_Bus&k=wdHsQuqY0Mqq1fNjZGIYnA%3D%3D%0A&r=FUxH%2FBfnuShktNQeewIrbzi32Zv3V%2BiOT0vbyv4h15w%3D%0A&m=7QOgGhzkereX6CVEmuBhvs1jwUpcawRZ2W61sFkl3kw%3D%0A&s=faf855c4e73d722970f089cc7f71d591aebc0cdf405606f8bb15cbe70fc25636> 3101 Park Blvd, Palo Alto, CA 94306
