[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: |
|
||||||||||||||||
| 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.
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: (cherry picked from commit ccaadff2491cd1758157358101df1636a3da9c96) GitOrigin-RevId: a8fc78364702dff511d72ecb15b1c3a2c8ba29b2 |
| Comment by Githook User [ 23/Jan/24 ] |
|
Author: {'name': 'James Bronsted', 'email': 'james.bronsted@mongodb.com', 'username': 'jpbronsted'}Message: (cherry picked from commit ccaadff2491cd1758157358101df1636a3da9c96) GitOrigin-RevId: 57b83eb55016194eb8228b62b493c3ae809c421c |
| Comment by Githook User [ 23/Jan/24 ] |
|
Author: {'name': 'James Bronsted', 'email': 'james.bronsted@mongodb.com', 'username': 'jpbronsted'}Message: (cherry picked from commit ccaadff2491cd1758157358101df1636a3da9c96) GitOrigin-RevId: 1f860e2ea270b8ec65e5a11d06ece80a65d29b88 |
| Comment by Githook User [ 22/Sep/23 ] |
|
Author: {'name': 'James Bronsted', 'email': 'james.bronsted@mongodb.com', 'username': 'jpbronsted'}Message: |
| 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? |