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:

• Command Monitoring and Logging
• Connection Monitoring and Pooling

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.