To facilitate general debugging and coverage metrics for randomized rollback testing, we should add additional logging into the rollback process that describes what is being done more comprehensively. This may include the following:

• Details of every operation that is being rolled back (i.e. oplog entry)
• A summarized version of the FixUpInfo struct after it has been populated
• An easily machine readable count of how many operations of each type were rolled back (for randomized coverage metrics)
• Improve the way common point timestamps are printed. Should be optime format as opposed to human readable date
• Fix the way the count of refetched docs is computed. It prints the size of an std::unordered_map whose keys are UUIDs of collections, but it should be a count of documents.

These messages could be placed at a higher log level that we can enable in our tests.