When symbolizing stack traces on secondary or initial syncing nodes, stack traces containing functions that accept the OplogEntry class such as applyCommand_inlock() and applyOperation_inlock() currently print the oplog entry as "...". In these scenarios, it would be useful for triaging purposes to see what kind of oplog entry the node is stuck trying to apply. It would be nice for the symbolizer/hang analyzer to use a pretty printer that allows us to see some basic information on the oplog entry such as timestamp and operation/command type in the stack trace.