Rotating specified log files
Run one of the following utilities to rotate a particular log file. On Windows, set up scheduled tasks that run the utilities. On UNIX, write a cron job that periodically runs the utilities. The behavior is the same on both Windows and UNIX, except as noted.
The following command (which is available for both the correlator and the IAF) instructs the component to close its component-specific log file and start using a new log file that has the name you specify. If the name of the file contains blanks, be sure enclose it in quotation marks.
engine_management --setLogFile log-filename
The following command (which is only available for the correlator) instructs the correlator to use the specified file as the log file for the specified node, which can be a package, monitor, or event. See also
Setting EPL log files and log levels dynamically.
engine_management --setApplicationLogFile [node=]log-filename
If you use separate log files for particular packages, monitors, or events you might want to rotate those log files at the same time that you rotate the main correlator log file. This keeps your Apama log files in sync with each other. See
Rotating all correlator log files.
On Windows, when you rotate a log file, you must ensure that the new log filename is different from the name of the log file that was in use. Apama takes care of this for you if you specify ${ROTATION_TIME} and/or ${ID} in the log-filename specification. If the name is not different, the old file is overwritten. If you want to use the same log filename, then you must move the file before you rotate it.
On UNIX, a log file is never overwritten. If you rotate a log file and specify the same name, then Apama appends messages to the content already there.
Apama does not support automatic log file rotation based on log file size.
The only way to rotate the correlator input log is to rotate all correlator log files. See
Rotating all correlator log files.