[DRIVERS-2703] Add TopologyID to all log messages Created: 23/Aug/23  Updated: 25/Sep/23

Status: Backlog
Project: Drivers
Component/s: Logging
Fix Version/s: None

Type: Improvement Priority: Unknown
Reporter: Preston Vasquez Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: FY24Q4
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by GODRIVER-2940 Add TopologyID to all log messages Closed
Driver Changes: Needed

 Description   

Summary

It could happen that multiple mongo clients write to the same log file. To make the logs easier for users to parse, we should include the client-unique topology id in each log message.

The SDAM specifications already include TopologyID. This ticket proposes including TopologyID in the following specifications:

Open question: should we include TopologyID in server selection? These logs should already include a topology description.

Motivation

Including the client-unique topology id in each log message will help make logging easier to parse, especially in cases where the user is pooling clients.


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