[DRIVERS-2452] Add databaseName property to command events Created: 27/Sep/22  Updated: 03/Oct/23

Status: Implementing
Project: Drivers
Component/s: Command Logging and Monitoring
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Tom Selander Assignee: Qingyang Hu
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to CXX-2651 Add databaseName property to command ... Backlog
split to MOTOR-1094 Add databaseName property to command ... Backlog
split to NODE-5055 Add databaseName property to command ... Backlog
split to RUBY-3220 Add databaseName property to command ... Backlog
split to RUST-1599 Add databaseName property to command ... Backlog
split to PHPC-2255 Add databaseName property to command ... Blocked
split to PHPLIB-1080 Sync spectests for Command Events dat... Blocked
split to CDRIVER-4572 Add databaseName property to command ... In Code Review
split to CSHARP-4520 Add databaseName property to command ... Closed
split to GODRIVER-2752 Add databaseName property to command ... Closed
split to JAVA-4875 Add databaseName property to command ... Closed
split to PYTHON-3598 Add databaseName property to command ... Closed
Related
related to DRIVERS-2575 Add collection name to all command lo... Backlog
is related to DRIVERS-1409 Add CommandStartedEvent to CommandSuc... Closed
is related to GODRIVER-1761 CommandFinishedEvent have not db name... Closed
is related to GODRIVER-2558 Add field Database with CommandFinish... Closed
Driver Changes: Needed
Downstream Changes Summary:
Start date:
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4572 In Code Review
CXX-2651 Backlog
CSHARP-4520 Done 2.21.0
GODRIVER-2752 Fixed 1.13.0, 1.13.1
JAVA-4875 Fixed 4.11.0
NODE-5055 Backlog
MOTOR-1094 Backlog 3.4
PYTHON-3598 Done 4.6
PHPLIB-1080 Blocked
RUBY-3220 Backlog
RUST-1599 Backlog
SWIFT-1702 Won't Do
PHPC-2255 Blocked

 Description   

Original Go ticket report:
GODRIVER-1761 requests that a databaseName property be added to CommandFailedEvent because storing the corresponding CommandStartedEvent and then retrieving it via the requestId field requires keeping a thread-safe map and the user says that this hurts their performance in highly concurrent applications.

Original DRIVERS ticket that was closed (for context): DRIVERS-1409.

It was decided during triage of DRIVERS-1409 that we just want to do this for databaseName only and nothing more, so we are closing that out and creating this ticket just to do databaseName.



 Comments   
Comment by Githook User [ 26/Jun/23 ]

Author:

{'name': 'Qingyang Hu', 'email': '103950869+qingyang-hu@users.noreply.github.com', 'username': 'qingyang-hu'}

Message: DRIVERS-2452 Add database name to the "command failed" and "command succeeded" log messages (#1436)
Branch: master
https://github.com/mongodb/specifications/commit/6b267ddc7cca303a722d2893106fad4810709f06

Comment by Githook User [ 21/Jun/23 ]

Author:

{'name': 'Qingyang Hu', 'email': '103950869+qingyang-hu@users.noreply.github.com', 'username': 'qingyang-hu'}

Message: DRIVERS-2452 Add databaseName field to CommandFailedEvent and CommandSucceededEvent (#1434)
Branch: master
https://github.com/mongodb/specifications/commit/e7ee829329400786e01279b4f37d4e440d1e9cfa

Comment by Jeffrey Yemin [ 08/Feb/23 ]

What about CommandSucceededEvent?

Comment by Kaitlin Mahar [ 27/Sep/22 ]

Note that to test this we probably need to update the unified test format to add databaseName expectations to expectedCommandEvent.commandSucceededEvent and expectedCommandEvent.commandFailedEvent.

Generated at Thu Feb 08 08:25:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.