Deploying and Managing Apama Applications > Event Correlator Utilities Reference > Replaying an input log to diagnose problems
Replaying an input log to diagnose problems
When you start the correlator, you can specify that you want it to copy all incoming messages to a special file, called an input log. An input log is useful if there is a problem with either the correlator process or an application running on the correlator. If there is a problem, you can reproduce correlator behavior by replaying the messages captured in the input log. Incoming messages include the following:
*Events
*EPL
*Java
*Correlator Deployment Packages (CDPs)
*Connection, deletion, and disconnection requests
If you are unable to diagnose the problem, you can provide the input log to Software AG Global Support. A support engineer can then feed your input log into a new correlator to try to diagnose the problem.
The information in the following topics describes how to generate and use an input log:
*Creating an input log
*Rotating the input log
*Command line examples for creating an input log
*Performance when generating an input log
*Reproducing correlator behavior from an input log
Copyright © Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or its Subsidiaries and or/its Affiliates and/or their licensors.
Use, reproduction, transfer, publication or disclosure is prohibited except as specifically provided for in your License Agreement with Software AG.