Deploying and Managing Apama Applications > Event Correlator Utilities Reference > Using a replay log to diagnose problems > Creating a replay log
Creating a replay log
To create a replay log, specify one of the following options when you start a correlator:
--replayLog filename[${START_TIME}][${ID}].log
--inputLog filename[${START_TIME}][${ID}].log
Option
Description
--replayLog
Indicates that you want to generate a full replay log. See Comparison of full replay logs and input-only replay logs.
--inputLog
Indicates that you want to generate a replay log from only input events. Both input-only replay logs and full replay logs record incoming events from engine_send and operations that change the contents of the correlator, such as engine_inject, engine_delete, or equivalents, and record connections and disconnections.See Comparison of full replay logs and input-only replay logs.
filename
Replace filename with the name of the file that you want to be the replay log. If you also specify ${START_TIME} and/or ${ID}, the correlator prefixes the filename you specify to the time the file was started and/or an ID, beginning with 001. See Command line examples for creating a replay log.Be sure to specify a location that allows fast access. If you specify the name of a file that exists, the correlator overwrites it.
${START_TIME}
Tag that indicates that you want the correlator to insert the date and time that it starts sending messages to the replay log into the filename of the replay log. Optional, however you probably want to always specify this option to avoid overwriting replay logs. See Command line examples for creating a replay log. This tag is also useful for correlators that you start from Apama’s Management and Monitoring console, because it lets you distinguish the replay logs from different correlators.
${ID}
Tag that indicates that you want the correlator to insert a three-digit ID into the filename of the replay log. The ID that the correlator inserts first is 001. Optional. The ID allows you to break up the replay log into a sequence of replay logs. A sequence of replay logs have the same name except for the ID. The log ID increment is related only to the specification of the rotate log option when you run the engine management tool. To rotate the replay log, invoke the engine_management utility and specify the -r rotateReplayLog option. Each time you rotate the log, the correlator closes the replay log it was using and starts a new replay log file and increments the ID portion of the filename by 1. See Command line examples for creating a replay log. This tag is useful when you plan to rotate the replay log. See the next topic for details. Note that restarting the correlator always resets the ID portion of the replay log filename to 001.
In addition, specify any other options that you would normally specify when you start the correlator.
Copyright © 2013 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.