[SERVER-24615] Enhance Egress Metadata Hook support using OperationContext Created: 15/Jun/16  Updated: 17/Jan/17  Resolved: 26/Jul/16

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 3.3.11

Type: Task Priority: Major - P3
Reporter: Mark Benvenuto Assignee: Mark Benvenuto
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-72 handshake optional parameters for dri... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.2
Sprint: Platforms 17 (07/15/16), Platforms 18 (08/05/16)
Participants:

 Description   

Enhance NetworkASIO to send the client metadata document. We will need to ensure that it captures the relevant information as part startCommand instead of the current metadata design in NetworkASIO. Further investigation is required.



 Comments   
Comment by Githook User [ 26/Jul/16 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-24615 Add support for OperationContext in EgressMetadataHook
Branch: master
https://github.com/mongodb/mongo/commit/1febb4ceb0e59743b0a49af35db10c4c689aa130

Comment by Githook User [ 26/Jul/16 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-24615 Update Auditing to use OperationContext in EgressMetadataHook
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/03933426ba344c1ba3a77f1ba07d51bf69803a33

Generated at Thu Feb 08 04:06:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.