title: Disable LocalCluster Logging in Apache Storm
body: <p>I'm trying to get started with Apache storm by running the <a href="https://github.com/apache/storm/tree/master/examples/storm-starter/src/jvm/storm/starter" rel="nofollow noreferrer">example code</a>. I'm working with storm 0.10.1-beta1 off of a maven repository. </p>
  
  <p>Unfortunately, when I run these, the console is flooded with info level logs, drowning out any <code>System.out.print()</code> calls that I've added. Is it possible to change the log level when running off of a LocalCluster? I've tried the solutions listed <a href="https://stackoverflow.com/questions/18206821/how-to-disable-turn-off-the-logging-feature-from-storm">here</a> and none of the solutions seem to be working.</p>
  
  <p>From the link, Changing the <code>Config.TOPOLOGY_DEBUG</code> property to false doesn't remove the info level logs, and using the code from the link, I can't even use <code>logger.setLevel((Level) Level.FATAL)</code> as I get "The method setLevel(Level) is undefined for the type Logger" despite it clearly being listed in the log4j api.</p>
  
  <p><strong>Edit 1</strong>:
  I also tried the solution <a href="https://stackoverflow.com/questions/30923617/how-to-implement-log-changes-in-a-storm-project-locally-using-eclipse/">here</a> and I put an xml called <code>logback.xml</code> into ./src with the following config:</p>
  
  <pre><code>&lt;configuration monitorInterval="60"&gt;
    &lt;Appenders&gt;
      &lt;Console name="Console" target="SYSTEM_OUT"&gt;
       &lt;PatternLayout pattern="%-4r [%t] %-5p %c{1.} - %msg%n"/&gt;
      &lt;/Console&gt;
    &lt;/Appenders&gt;
    &lt;Loggers&gt;
      &lt;Logger name="org.apache.zookeeper" level="WARN"/&gt;
      &lt;Root level="WARN"&gt;
        &lt;AppenderRef ref="Console"/&gt;
      &lt;/Root&gt;
    &lt;/Loggers&gt;
  &lt;/configuration&gt;
  </code></pre>
  
  <p>Still no luck though. Is there any additional config required to tell storm to use the custom log settings?</p>
  
  <p><strong>Update:</strong> It turns out that storm 0.10.x switched to using log4j2 instead of logback, so adding a log4j2.xml with the configuration above finally worked!</p>