Skip to end of metadata
Go to start of metadata

Overview

Since version v1.5.3100-beta of the JobScheduler Engine it is possible to configure a logging API of your choice to handle the log messages from JobScheduler (assumed the logging API is supported by slf4j). Using this feature you have a wide range of possibilities to handle your logs, e.g. filtering, mailing, eventing etc.

JobScheduler was currently shipped with the nop-api for slf4j. That means that no messages from JobScheduler logged via a logging api.

But beside the configuration of a logging API such as logback or log4j the logging in the "old style" is supported until further notice. That means that you will always find the scheduler logs and the logs of your jobs in the folder logs located of your JobScheduler installation.

Installation in general

Have a look at factory.ini to will find a property like class_path in the java section:

This is the place where you can subtitute the nop api with a real logging api like logback.

Put the necessary libraries for the logging api of your choice into a separate folder and point to the jars of this folder in factory.ini instead to ${SCHEDULER_HOME}/lib/log/nop/*.jar.

Relationship between the configuration for the logging API and factory.ini

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 full control of all log messages from JobScheduler then you should specify

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

The setting of the property log in the factory.ini file causes the Job Scheduler to write a detailed protocol. This protocol is intended for use in problem diagnosis. The file name should be specified here as a full path. A plus character + written directly before the file name causes an already existing protocol to be continued. Otherwise such a protocol will be overwritten.

Examples:

Using log4j

To configure log4j for the JobScheduler Engine add a log4j configuration file (log4j.properties) to a directory of your choice and reference it by setting the java system property log4j.configuration, e.g. -Dlog4j.configuratioh1. file:///path/to/log4j.properties

Installation

Create the folder ./lib/log/log4j in the installation path of JobScheduler you should modify the property class_path as follows:

The folder log4j has to contain the slf4j-log4j12-x.jar file, e.g. slf4j-log4j12-1.7.5.jar.
Make sure that log4j-1.2.16.jar is located in the ./lib directory.

Sample configuration

Start of JobScheduler

To use the configuration above you have to start JobScheduler by setting the options property (section [java]) in your ./config/factory.ini, e.g.

Logging to a syslog server

Log4j offers a SyslogAppender to send log entries to a syslog receiver. This Appender is not explicitely tested by us but it seems to be straight foward to use this appender.

Example

Using logback: To configure logback for the JobScheduler Engine put a logback configuration file into a directory of your choice and reference it by setting the java system property logback.configurationFile, e.g. -Dlogback.configurationFilefilename

Installation

As described above you have to create a separate folder containing the required jar files to use logback. Assuming your are creating the folder lib/log/logback in the installation path of JobScheduler then you should modify the property class_path as follows:

The folder logback has to contain at least logback-core and logback-classic, e.g.

  • logback-classic-1.0.11.jar
  • logback-core-1.0.11.jar

Sample configuration

The logger JobScheduler controls the output of the Main Log File (see Logs in the JobScheduler documentation for details).

Please note that the file element of a FileAppender can not contain a relative path (see do not use relative path with logback for details).

Start of JobScheduler

To use the configuration above you have to start JobScheduler by setting the options property (section [java]) in your ./config/factory.ini, e.g.

Logging to a syslog server

Logback offers a SyslogAppender to send log entries to a syslog receiver. This Appender is not explicitely tested by us but it seems to be straight foward to use this appender.

See Appenders in the logback manual for details.

Mapping of the JobScheduler log levels

The log levels used by JobScheduler are mapped as follows (highest to lowest):

JobScheduler log levels

slf4j log level

error

error

warn

warn

info

info

debug, debug1, debug2

debug

debug3 and higher

trace