Configuring Change Logging

Its default location is:

wildfly-x.y.z/standalone/configuration/standalone.xml

where x.y.z are the version, subversion, and patch numbers.

To enable change logging, search for the following fragment and change OFF to INFO:

<logger category="com.fico.xpress.insight-data-changes">
  <level name="OFF"/>
  <handlers>
    <handler name="INSIGHT_DATA_CHANGE_FILE"/>
  </handlers>
</logger>

To configure the log file rotation policy, search for the following fragment:

<periodic-rotating-file-handler name="INSIGHT_DATA_CHANGE_FILE">
  <file relative-to="jboss.server.log.dir" path="insight-data-changes.log"/>
    <formatter>
      <pattern-formatter pattern="%d{HH:mm:ss,SSS} %s%E%n"/>
    </formatter>
   <suffix value=".yyyy.MM.dd"/>
   <append value="true"/>
</periodic-rotating-file-handler>

By default, a periodic rotating file handler is used to rotate/renew the log file at a specified frequency as defined by the <suffix> element shown above. The default configuration does this daily, but you can change it - for example, the following configuration rotates the log file hourly:

<suffix value=".yyyy.MM.dd.HH"/>

WildFly allows a rotating file handler to be defined in other ways as well. You can configure it to allow a specified number of log files to be retained that are of a specific size. The following example illustrates:

<size-rotating-file-handler name="INSIGHT_DATA_CHANGE_FILE">
  <file relative-to="jboss.server.log.dir" path="insight-data-changes.log"/>
 	<rotate-size value="1m"/>
 	<max-backup-index value="10"/>
 	<append value="true"/>
 	<formatter>
    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %s%E%n"/>
 	</formatter>
</size-rotating-file-handler>

Here, a log file is renamed with a suffix of .1 and a new log file created when the log file size exceeds 1MB.