You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

To configure logback for the JobScheduler engine put a logback configuration into a directory of you choice and reference it by setting the java system property logback.configurationFile, e.g.
-Dlogback.configurationFilh1. etc/logback.xml.

A sample configuration:

<configuration>

   <appender name="STDERR" class="ch.qos.logback.core.ConsoleAppender">
       <encoder>
           <pattern>%d\{dd HH:mm:ss\} [%thread] %-5level %logger - %msg%n</pattern>
       </encoder>
   </appender>
   
   <appender name="FILE" class="ch.qos.logback.core.FileAppender">
    <file>$\{user.dir\}/logs/logback-test.log</file>
    <append>false</append>
    <encoder>
           <pattern>%d\{dd HH:mm:ss\} [%thread] %-5level %logger - %msg%n</pattern>
    </encoder>
  </appender>

   <root level="WARN">
       <appender-ref ref="STDERR" />
   </root>
   
   <logger name="JobScheduler" level="TRACE" additivity="false">
       <appender-ref ref="FILE" />
   </logger>
   
</configuration>

The logger JobScheduler controls the output of the JobScheduler engine.

The setting of the property log_level in the factory.ini filters the messages that will be available for slf4j. That means, that the level you set in the factory.ini should never be higher than the level you have specified in the logger JobScheduler. If you want a full control of all log messages from JobScheduler you should specify

 log_level = debug9

in factory.ini but be aware the log files can be very large.

Beside the configuration of a logging API such logback the logging in the "old style" is supported until further notice.

Conversion of the JobScheduler log levels

The log levels used by JobScheduler are converted as follows:
\ style"background-color:#ffffcc;" cellpaddinh1. "20" cellspacing"0" bordeh1. "1"

width"15%" aligh1. "left"

JobScheduler log levels

width"15%" align="left"

slf4j log level

-

error

error

-

warn

warn

-

info

info

-

debug, debug1, debug2

debug

-

debug3 and higher

trace

-

  • No labels