Set up log file automatic rollover

This topic addresses setting up automatic rollover of log files based on the file size.

After the log files are created, the system continues logging messages, which increases the log file size to a point where they are too large to open. This prevents the user from opening the log files for reviewing the information and error messages.
Note:
  • This happens sooner if the logging level is increased to DEBUG or TRACE modes.
  • To ensure smooth operation of the system, manual clear the logs periodically.
For all Java services, user can identify the log files under <IQ Bot installation directory>/Services . Open any logging configuration file, and add the following change under <SizeBasedTriggeringPolicy size="100MB" /> in the first occurrence of Policies:

<Policies>
<TimeBasedTriggeringPolicy interval="720" />
<SizeBasedTriggeringPolicy size="50MB" />
</Policies>

In the following example setting, after the log file reaches 50 MB, the system creates a new file automatically and starts logging in it. Though the user ends up with more files, but each file would be 50 MB only. This is standard practice to manage log files.

This example shows entries a user can add to the setting for Automation 360 IQ Bot On-Premises to automatically roll over the logs after the files reach a certain size.

<RollingFile name="Alias" fileName="${env:PUBLIC}/Documents/Automation Anywhere IQBot Platform/Logs/Alias.log"
                     filePattern="${env:PUBLIC}/Documents/Automation Anywhere IQBot Platform/Logs/Archive/${date:yyyy-MMM}/Alias-%d{yyyy-MMM-dd}-%i.log.zip"
                     immediateFlush="true"
                     append="true">
            <PatternLayout pattern="CPL1 Alias %X{cid} %d{ISO8601}{UTC}Z %-5level %C %M %msg %n"/>
            <Policies>
                <TimeBasedTriggeringPolicy />
                <SizeBasedTriggeringPolicy size="50MB" />
            </Policies>
            <DefaultRolloverStrategy max="10"/>
        </RollingFile>