Details
Description
To better identify if network compression is being used by client applications via the drivers it would be helpful to have successful compressor negotiation messages logged ad the default log level.
{"t":{"$date":"2023-08-16T13:28:06.636-04:00"},"s":"D3","c":"NETWORK","id":22937,"ctx":"conn12","msg":"supported compressor","attr":{"compressor":"zlib"}}
|
When the MessageCompressorManager logs a successful negotiation it is at D3 verbosity, which won't be printed to mongos/mongod logs.
Attachments
Issue Links
- related to
-
DRIVERS-1335 Improve Awareness of Network Compressors for Drivers
-
- Backlog
-
-
SERVER-79842 Differentiate serverStatus.network.compression by internal and external sources
-
- Closed
-