We have many (>1) applications making changing to the same collections it would be nice to determine which client/application instigated the change in the database.

Currently the only solution is maintaining some state in the object itself.

Ideally when we listen to stream.on('change', (change, clientSession) => { } );
a new clientSession parameter could be provided. This would be the clientSession of the process that inserted/updated/deleted the object, not the local listener clientSession.

Is this possible?
TIA
Kevin Fairclough