"configurator-log" RollingFile Appender

This appender manages configurator logs with automatic file rotation.

Configuration example:

<Appenders>
    <RollingFile name="configurator-log" fileName="logs/configurator.log" filePattern="logs/configurator-%d{yyyy-MM-dd}.log">
        <PatternLayout pattern="%d %-5p [%c] - %m%n"/>
        <Policies>
            <SizeBasedTriggeringPolicy size="256MB"/>
        </Policies>
        <DefaultRolloverStrategy max="10"/>
    </RollingFile>
</Appenders>

Example Log :

2025-01-14 11:19:56,054 INFO  [com.okiok.sfiler.configurator.web.filter.HttpSecurityConfiguratorFilter] - HTTP Security Filter has been initialized.

Log details:

1. 2025-01-14 11:19:56,054 : Date and time of the log
2. INFO : Log level
3. [com.okiok.sfiler.configurator.web.filter.HttpSecurityConfiguratorFilter] : Class name generating the log
4. - HTTP Security Filter has been initialized. : Log message

Basic Configuration

The configuration of this log is found in the following path: [installation directory]/server/webapps/sfiler-configurator/WEB-INF/classes/log4j2.xml

• Name: configurator-log
• Output file: logs/configurator.log
• Archive file pattern: logs/configurator-[DATE].log

Log Format

The pattern %d %-5p [%c] - %m%n defines the following format:

• %d : Log date and time
• %-5p : Log level (DEBUG, INFO, ERROR...) aligned to 5 characters
• [%c] : Class name generating the log
• %m : Log message
• %n : Line break

Rotation Policy

• SizeBasedTriggeringPolicy: 256MB per file
• DefaultRolloverStrategy: Maximum 10 archive files
• Rotation creates a new file when:
  • Current file reaches 256MB
  • A new day begins (based on date pattern)

Characteristics

• Format particularly suitable for:
  • Configuration changes tracking
  • System changes auditing
  • Configuration issues diagnosis
  • Configurator updates traceability

References

• Log4j2 RollingFile Appender