This page describes how to configure the logging in the different component of Step.

Controller logs

Per default the controller logs are written to the file log/controller.log.

The default logging settings can be changed in the file bin/logback.xml.

Verbosity

You can easily change the logging verbosity by tweaking the “root” log level present in the file bin/logback.xml. Below an example with the root log level verbosity set to error :

<configuration scan="true">
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
 <file>../log/controller.log</file>
 <encoder>
  <pattern>%date %level [%thread] %logger{10} [%file:%line] %msg%n</pattern>
 </encoder>
 <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
     <fileNamePattern>../log/controller.%d{yyyy-MM-dd}.log</fileNamePattern>
     <maxHistory>30</maxHistory>
   </rollingPolicy>
</appender>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
 <encoder>
  <pattern>%msg%n</pattern>
 </encoder>
</appender>

<root level="error">
 <appender-ref ref="STDOUT" />
 <appender-ref ref="FILE" />
</root>
</configuration>

Audit logs

Security-relevant events such as user login/logout, session invalidation, and password changes are logged using the special logger AuditLogger.

Step Enterprise already ships a tailored log configuration which logs these events to the file audit-logger.log in the log/ directory.

Agent logs

Java Agent

Per default the logs of the Java Agent are written to the file log/agent.log.

The default logging settings can be changed in the file bin/logback.xml.

.NET Agent

Per default the logs of the Java Agent are written to the file log/agent.log.

The default logging settings can be changed in the file bin/StepAgent.dll.config.