anchor.diff:  === Logical connector name
   
   The connector configuration property `mongodb.name` serves as a _logical name_ for the MongoDB replica set or sharded cluster.
  -The connector uses the logical name in a number of ways: as the prefix for all topic names, and as a unique identifier when recording the oplog/change stream position of each replica set.
  +The connector uses the logical name in a number of ways: as the prefix for all topic names, and as a unique identifier when recording the change stream position of each replica set.
   
   You should give each MongoDB connector a unique logical name that meaningfully describes the source MongoDB system.
   We recommend logical names begin with an alphabetic or underscore character, and remaining characters that are alphanumeric or underscore.
  
positive.code: * Names of the collection and database that contain the new document.
  * If the event was part of a snapshot.
  * Timestamp for when the change was made in the database and ordinal of the event within the timestamp.
  * Unique identifier of the MongoDB operation, which depends on the version of MongoDB. It is either the `h` field in the oplog event, or a field named `stxnid`, which represents the `lsid` and `txnNumber` fields from the oplog event (oplog capture mode only).
  * Unique identifiers of the MongoDB session `lsid` and transaction number `txnNumber` in case the change was executed inside a transaction (change streams capture mode only).
  
  |8
  
negative.code: After the connector starts, it completes the following actions:
  
  * xref:{link-mongodb-connector}#mongodb-performing-a-snapshot[Performs a consistent snapshot] of the collections in your MongoDB replica sets.
  * Reads the change streams for the replica sets.
  * Produces change events for every inserted, updated, and deleted document.
  * Streams change event records to Kafka topics.
  
  