.WEBPIECESxAPPNAME-dev.1.9.137.source-code.logback.xml Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of WEBPIECESxAPPNAME-dev Show documentation

Someone forgot to fill this in. See http://stackoverflow.com/questions/38272550/how-to-fail-the-gradle-build-if-subproject-is-missing-a-property

There is a newer version: 2.1.28

Show newest version

<?xml version="1.0" encoding="UTF-8" ?>
<configuration scan="true" scanPeriod="30 seconds">
	<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
	    <filter class="ch.qos.logback.core.filter.EvaluatorFilter">      
	      <evaluator class="ch.qos.logback.classic.boolex.GEventEvaluator"> 
	        <expression>
	           e.level.toInt() &lt;= INFO.toInt()
	        </expression>
	      </evaluator>
	      <OnMismatch>DENY</OnMismatch>
	      <OnMatch>NEUTRAL</OnMatch>
	    </filter>
    
		<encoder>
			<pattern>%date{ISO8601} [%X{txId}-%X{user}] [%thread] %caller{1..2} %-4level: %message%n</pattern>
		</encoder>
	</appender>

	<appender name="STDERR" class="ch.qos.logback.core.ConsoleAppender">
		<filter class="ch.qos.logback.classic.filter.ThresholdFilter"> 
    	    <level>warn</level>
    	</filter>
    
		<encoder>
			<pattern>%date{ISO8601} [%X{txId}-%X{user}] %caller{1..2} %-4level: %message%n</pattern>
		</encoder>
		<target>System.err</target>
	</appender>
	
    <!--  these can effect performance greatly, if doing any performance testing uncomment these lines! -->
    <!--  hierarchical entries left on purpose to make it easier to get just what you want  -->
    <!--  com.alvazan.orm.logging is particularly brutal for performance, always set to at least WARN except in dev env -->
    
    <!-- this config will be the least verbose: -->
    <logger name="com.alvazan.orm" level="WARN"/>
    <!--logger name="controllers" level="WARN"/-->
    <!--logger name="org.playorm.cron" level="WARN"/-->
    
    <logger name="controllers.modules2.DataFillerProcessor" level="DEBUG"/>
    <!-- this config is a little more verbose, comment out any given line to be more verbose: -->
    <!--logger name="com.alvazan.orm.logging" level="WARN"/-->
    <!--logger name="com.alvazan.orm.parser.antlr" level="WARN"/-->
    <!--logger name="com.alvazan.orm.layer5.nosql.cache" level="WARN"/-->
    <!--logger name="controllers.modules" level="WARN"/-->
    <!--logger name="controllers.modules.util" level="WARN"/-->
    <!--logger name="controllers.modules2.framework" level="WARN"/-->
    <!--logger name="controllers.modules2.framework.procs" level="WARN"/-->
    <!--logger name="controllers.modules2" level="WARN"/-->
    <!--logger name="play.server" level="WARN"/-->
    <logger name="jdbc.sqlonly" level="INFO"/>
    <logger name="jdbc.sqltiming" level="WARN"/>
    <logger name="jdbc.audit" level="WARN"/>
    <logger name="jdbc.resultset" level="WARN"/>
    <logger name="jdbc.connection" level="WARN"/>
    
    <!-- this will crush performance if uncommented, but it's useful to see interactions with cassandra.  Leave it commented out unless you know what you are doing. -->
    <!-- logger name="com.alvazan.orm.layer9z.spi.db.cassandra.CassandraSession" level="TRACE"/ -->
  
	<root>
		<level value="INFO" />
		<appender-ref ref="STDOUT"/>
		<appender-ref ref="STDERR"/>
	</root>
</configuration>