-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Component/s: Command Logging and Monitoring
-
None
-
Needed
-
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.
- is related to
-
DRIVERS-1409 Add CommandStartedEvent to CommandSucceedEvent/CommandFailedEvent
- Closed
-
GODRIVER-1761 CommandFinishedEvent have not db name property
- Closed
-
GODRIVER-2558 Add field Database with CommandFinishedEvent
- Closed
- related to
-
DRIVERS-2575 Add collection name to all command logging and monitoring events
- Backlog
- split to
-
PHPLIB-1080 Sync spec tests for command events databaseName property
- Closed
-
CXX-2651 Add databaseName property to command events
- Backlog
-
NODE-5055 Add databaseName property to command events
- Backlog
-
RUBY-3220 Add databaseName property to command events
- Backlog
-
RUST-1599 Add databaseName property to command events
- Backlog
-
CDRIVER-4572 Add databaseName property to command events
- Closed
-
CSHARP-4520 Add databaseName property to command events
- Closed
-
GODRIVER-2752 Add databaseName property to command events
- Closed
-
JAVA-4875 Add databaseName property to command events
- Closed
-
MOTOR-1094 Add databaseName property to command events
- Closed
-
PHPC-2255 Add databaseName property to command events
- Closed
-
PYTHON-3598 Add databaseName property to command events
- Closed