Apama Documentation : Deploying and Managing Apama Applications : Correlator Utilities Reference : Shutting down and managing components : Rotating all log files
Rotating all log files
To invoke rotation of all log files that the correlator is using, you can do the following:
*Invoke the engine_management tool and specify --rotateLogs.
This rotates the correlator status log, the sentinel agent status log, the correlator input log if it is being generated, and any application logs that are being generated. When you invoke this management request then the correlator closes each log file it was using.
If the log filename specification declared ${START_TIME}, ${ROTATION_TIME} and/or ${ID} then the correlator starts new log files with updated names according to the log filename specification, for example, if ${ID}was specified then the ID portion of a log filename would be incremented by 1.
*In EPL, create a monitor that uses the Management interface correlator plug-in to trigger log rotation on a schedule. See Using the Management interface.
*On UNIX only, you can write a cron job that periodically sends a SIGHUP signal to Apama processes.
The standard UNIX SIGHUP mechanism causes Apama processes to re-open their log files. If the log file names were specified with the ${ROTATION_TIME} and/or ${ID} then the re-opened files have names that contain the rotation time and/or the incremented ID.
If you want a log filename to always be the same and so did not declare ${START_TIME}, ${ROTATION_TIME} or ${ID} in the log filename specification then the correlator starts new log files that have the same names as the log files it closed. On Windows, this would overwrite the closed log files so you must move the log files before invoking rotation. On UNIX, log files are appended to if the names are the same.
Copyright © 2013-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback