Summary
The timestamp simulator will support a call log as an input,  indicating the operations performed as part of the test. WiredTiger will need to generate such a call log so that we can run the simulator on the same set of operations and compare the results. When an API is invoked / operation is performed in WiredTiger, corresponding call log entry will be generated through a helper function. The helper function will be enabled through compilation options like “enable-call_log”.

Motivation

• Does this affect any team outside of WT?
  No

• How likely is it that this use case or problem will occur?
  N/A

• If the problem does occur, what are the consequences and how severe are they?
  N/A

• Is this issue urgent?
  No

Acceptance Criteria (Definition of Done)
An empty call log file will be generated when the configuration options to generate the call log are included during compilation.

• Testing
  (What all testing needs to be done as part of this ticket? Unit? Functional? Performance?Testing at MongoDB side?)

• Documentation update
  (Does this ticket require a change in the architecture guide? If yes, please create a corresponding doc ticket.)

[Optional] Suggested Solution
(Is there any suggested solution to handle this issue? Is it related to any existing WT ticket? Is it related to any previous issue fixed? If yes, link the WT ticket number using related to, depends on, dependent on by links)