[SERVER-29109] Client metadata log message verbosity is not parallel with connection start/end messages Created: 08/May/17 Updated: 26/Jan/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 7 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v7.3
|
||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 146 | ||||||||||||||||||||||||||||||||||||
| Description |
|
One of the main behaviors of the --quiet command line switch is to suppress the "connection received" and "end connection" log messages. However, the new "received client metadata from" log message does not adhere to the --quiet switch. This means that users that used to be able to suppress a high volume of log messages from incoming connections no longer can do so. |
| Comments |
| Comment by Githook User [ 04/Jul/23 ] |
|
Author: {'name': 'dziana.hurynovich', 'email': 'dziana.hurynovich@mongodb.com', 'username': ''}Message: Revert "SERVER-29109 avoid logging client metadata when --quiet" This reverts commit ff2e82d06ba680bff895d3ff634881e48d746cb8. |
| Comment by Githook User [ 03/Jul/23 ] |
|
Author: {'name': 'Tyler Brock', 'email': 'tyler.brock@gmail.com', 'username': 'TylerBrock'}Message: SERVER-29109 avoid logging client metadata when --quiet |
| Comment by Eric Milkie [ 09/Nov/21 ] |
|
lauren.lewis yes. |
| Comment by Lauren Lewis (Inactive) [ 09/Nov/21 ] |
|
milkie is this still a user painpoint that exists today? |