From: Giovanni Meo <gmeo@cisco.com>
Date: Fri, 24 Jan 2014 08:53:03 +0000 (+0100)
Subject: Reduce informations from logging.bridge
X-Git-Tag: jenkins-controller-bulk-release-prepare-only-2-4~5^2
X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?p=controller.git;a=commitdiff_plain;h=refs%2Fchanges%2F85%2F4685%2F1

Reduce informations from logging.bridge

Logging bridge maps 1-1 the log level from OSGi logging service to
slf4j. By design the OSGi framework set al INFO level all the modules
start and stop, which by pure chance, is also inline with our
guideline. Even though the compliance is satisfied there is a
usability issue because the console is flooded with many start stop
events given there are many bundles hence setting to WARN level the
log level for logging.bridge

Change-Id: I0dc484c49bd5966ad7dcdc01d55b9c28cfcf8217
Signed-off-by: Giovanni Meo <gmeo@cisco.com>
---

diff --git a/opendaylight/distribution/opendaylight/src/main/resources/configuration/logback.xml b/opendaylight/distribution/opendaylight/src/main/resources/configuration/logback.xml
index 61d274d80c..a24a507840 100644
--- a/opendaylight/distribution/opendaylight/src/main/resources/configuration/logback.xml
+++ b/opendaylight/distribution/opendaylight/src/main/resources/configuration/logback.xml
@@ -41,7 +41,7 @@
   <logger name="org.opendaylight.controller" level="INFO"/>
 
   <!-- OSGi logging bridge -->
-  <logger name="org.opendaylight.controller.logging.bridge" level="INFO"/>
+  <logger name="org.opendaylight.controller.logging.bridge" level="WARN"/>
   <logger name="org.opendaylight.controller.logging.bridge.internal" level="WARN"/>
 
   <!-- Netty -->