When a change stream receive ChangeStreamHistoryLoss error it is not clear if the change stream is being resumed with a resume token using resumeAfter or startAfter option or started in the past using startAtOperationTime option.

Moreover, current there is a small discrepancy when emitting ChangeStreamHistoryLost error:

• in case of OplogQueryMinTsMissing error we return a user error and create an error log entry
• in case of IncompleteTransactionHistory error we return a user error, but no log entry is added

Normally, user errors are not logged.

In either cases, it would be nice to include the currently first oplog timestamp to the error message.

It would also help to be able to easily infer if the oplog was rotated 'naturally' or if it was truncated by the initial sync process.