[SERVER-80150] Log negotiated network compressor with client metadata Created: 16/Aug/23  Updated: 05/Feb/24  Resolved: 25/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0, 7.0.6, 5.0.25, 6.0.14

Type: Improvement Priority: Major - P3
Reporter: Alex Bevilacqua Assignee: James Bronsted
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to DRIVERS-1335 Improve Awareness of Network Compress... Backlog
related to SERVER-79842 Differentiate serverStatus.network.co... Closed
Assigned Teams:
Service Arch
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.0, v5.0, v4.4
Sprint: Service Arch 2023-09-18, Service Arch 2023-10-02
Participants:

 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.



 Comments   
Comment by Githook User [ 05/Feb/24 ]

Author:

{'name': 'James Bronsted', 'email': 'james.bronsted@mongodb.com', 'username': 'jpbronsted'}

Message: SERVER-80150 add negotiated compressor to client metadata log line

(cherry picked from commit ccaadff2491cd1758157358101df1636a3da9c96)

GitOrigin-RevId: a8fc78364702dff511d72ecb15b1c3a2c8ba29b2
Branch: v5.0
https://github.com/mongodb/mongo/commit/cfef25d6e057af581570d4092a44a3b231b947b6

Comment by Githook User [ 23/Jan/24 ]

Author:

{'name': 'James Bronsted', 'email': 'james.bronsted@mongodb.com', 'username': 'jpbronsted'}

Message: SERVER-80150 add negotiated compressor to client metadata log line

(cherry picked from commit ccaadff2491cd1758157358101df1636a3da9c96)

GitOrigin-RevId: 57b83eb55016194eb8228b62b493c3ae809c421c
Branch: v7.0
https://github.com/mongodb/mongo/commit/42ef5474666790ef13dceeb76a23abe7427a5a92

Comment by Githook User [ 23/Jan/24 ]

Author:

{'name': 'James Bronsted', 'email': 'james.bronsted@mongodb.com', 'username': 'jpbronsted'}

Message: SERVER-80150 add negotiated compressor to client metadata log line

(cherry picked from commit ccaadff2491cd1758157358101df1636a3da9c96)

GitOrigin-RevId: 1f860e2ea270b8ec65e5a11d06ece80a65d29b88
Branch: v6.0
https://github.com/mongodb/mongo/commit/c25e304106ed7b01839bf283ee5b3cd5ecf5b18f

Comment by Githook User [ 22/Sep/23 ]

Author:

{'name': 'James Bronsted', 'email': 'james.bronsted@mongodb.com', 'username': 'jpbronsted'}

Message: SERVER-80150 add negotiated compressor to client metadata log line
Branch: master
https://github.com/mongodb/mongo/commit/ccaadff2491cd1758157358101df1636a3da9c96

Comment by Jason Chan [ 12/Sep/23 ]

alex.bevilacqua@mongodb.com Could you let us know the priority/timeline for this?

Also, Service Arch has some concerns on increasing the default log level for the log message you indicated since it could flood the logs even more during high connection scenarios. Instead, we would propose adding the "compressor" field to the client meta data log message which is already printed at the default level whenever a client connection is accepted. Would this still work for your requirements?

Generated at Thu Feb 08 06:42:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.