-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Logging, Server Selection
The log line for "Waiting for suitable server to become available" is too noisy to be at level INFO, for example in the test suite:
[2024/03/05 08:26:06.602] ------------------------------ Captured log call ------------------------------- [2024/03/05 08:26:06.602] INFO pymongo.serverSelection:logger.py:94 {"message": "Waiting for suitable server to become available", "selector": "Primary()", "operation": "find", "topologyDescription": "<TopologyDescription id: 65e74798e1229616f1003db2, topology_type: ReplicaSetNoPrimary, servers: [<ServerDescription ('localhost', 27017) server_type: Unknown, rtt: None>]>", "clientId": {"$oid": "65e74798e1229616f1003db2"}, "remainingTimeMS": 29}
I think we should log this at DEBUG level instead, otherwise users are going to be confused. Essentially this line will be logged every time a client is first created and used.
- related to
-
PYTHON-4261 Log line for "Waiting for suitable server to become available" is too noisy
- Closed
-
DRIVERS-1671 Add log messages to Server selection spec
- Implementing