Logging Configuration File

This section describes the default logging configuration file along with some details common to Iotellect Server logging configuration.

The default logging configuration is represented by a root configuration element, two appenders (destinations for log output), and several named logging categories.

<?xml version="1.0" encoding="UTF-8" ?>
<Configuration monitorInterval="10">
  <Appenders>
    <Console name="console" target="SYSTEM_OUT">
     <ThresholdFilter level="debug"/>
     <PatternLayout pattern="%d{HH:mm:ss,SSS} %-5p %-25c %m - [%t] %C.%M (%F:%L)%n%throwable{full}"/>
    </Console>
    <RollingFile name="file" fileName="logs/server.log" append="true" filePattern="logs/server.%d{yyyy-MM-dd}.log">
     <ThresholdFilter level="debug"/>
       <PatternLayout pattern="%d{dd.MM.yyyy HH:mm:ss,SSS} %-5p %-25c %m - [%t] %C.%M (%F:%L)%n%throwable{full}" charset="UTF-8"/>
        <Policies>
          <TimeBasedTriggeringPolicy interval="1" modulate="true"/>
        </Policies>
    </RollingFile>
  </Appenders>
  <Loggers>
    <Logger name="ag" level="warn" additivity="false">
      <AppenderRef ref="file"/>
      <AppenderRef ref="console"/>
    </Logger>
    <Logger name="ag.alerts" level="info"/>
<!-- Other logging categories are skipped -->
    <Root level="warn">
      <AppenderRef ref="console"/>
      <AppenderRef ref="file"/>
    </Root>
  </Loggers>
</Configuration>

The root element (<Root>) defines the global logging level as warning (<Root level="warn">) (see logging levels for more information). It applies to all messages coming from the system libraries used by the server core.  

Logging of the server itself is performed using warn level. This is specified by the level="warn" attribute that is located in <Logger name="ag"...>element. To switch the server to debug-level logging in a certain category, change this tag to <level="debug"/>. The <Logger> elements define which level is used for logging from each subsystem of Iotellect Server.

This logging configuration also defines two appenders named console and file. An Appender is a destination for logging output. It can be a text file, e-mail message, etc.

RollingFilerequires a set of policies to determine when log file rollover (roration) should be performed.TimeBasedTriggeringPolicyis used by default which means that a rollover will be performed once a day. Different policies may be used simultaneously.

For more information, consult Log4j documentation.

Was this page helpful?