We receive far more information to log, starting with the 2.2 driver, with the help of event subscribers. However, in an async environment, it is hard to tell, if not impossible, which command that we issued matches a specific event (for example CommandSucceededEvent). Ideally, it would be very handy to provide in a BulkWriteAsync command, or FindAsync, some sort of information (string?) that we can get in the event information and then match with our custom code (for example in the Options parameter).

Alternatively, the result objects could provide a list of issued command ids related to that operation (BulkWrite/Find) - however I favor the first approach.