In PM-1950, we added a number of new change events, while also adding some new fields to existing events. In order to prevent disruption to users, we guarded both the new events and the new fields behind the opt-in showExpandedEvents flag. However, in the case of the new fields, this was likely an unnecessarily cautious approach; adding new fields, as opposed to modifying existing fields, does not violate the principle of the stable API. In fact, we already exposed the new wallTime field, which was originally behind the showExpandedEvents flag, in SERVER-65022.

We should reconsider whether it makes sense to move the remaining fields out from behind the expanded events flag, while continuing to keep the new events themselves behind it. The fields in question are:

• The collectionUUID field for applicable DML and DDL events.
• The disambiguatedPaths field for update events.
• The operationDescription field for pre PM-1950 events (specifically rename).