Deploying and Managing Apama Applications > Event Correlator Utilities Reference > Using a replay log to diagnose problems > Comparison of full replay logs and input-only replay logs
Comparison of full replay logs and input-only replay logs
You can generate two different kinds of replay logs:
*A full replay log lets you replay the exact same behavior, ordering of emit operations, and so on, as the run that generated the replay log.
*An input-only replay log contains only the external inputs to the correlator. There is no information about multi-context ordering. Consequently, if there is more than one context, there is no guarantee that you can replay execution in the same order as the original execution.
Following is a comparison of full and input-only replay logs:
*Input-only replay logs are smaller and the correlator can write them faster than full replay logs.
*Full replay logs always generate the same output and state. Input-only replay logs generate the same output and state only when there is a single context.
*Both full replay logs and input-only replay logs contain information that is sufficient for auditing what events were sent to 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.