[SERVER-27663] Informational Network component log messages should be configurable Created: 12/Jan/17 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 3.4.1 |
| Fix Version/s: | features we're not sure of |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Arhelger | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 3 |
| Labels: | 4amigos, features-not-sure-of | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
Currently, informational log messages for the network component in both (mongos and mongod) are always logged. Some users would like to disable the logging of messages such as:
In cases where a load balancer is used, these messages yield little information and could contribute to additional IO should the connection churn be great. Currently, the only approach is to disable logging entirely through setting quiet=true |
| Comments |
| Comment by Kevin Arhelger [ 10/Nov/21 ] |
|
This request is not very common, I can't recall any instances outside of this one. In general it would be nice to configure this, even if its not something we recommend, but I don't believe there is a strong desire to eliminate these messages. |
| Comment by Lauren Lewis (Inactive) [ 09/Nov/21 ] |
|
kevin.arhelger is this still relevant today? cc: shameek.ray |
| Comment by Mohamed Meabed [ 18/May/17 ] |
|
Understand its critical, we don't want it to be removed, but could we have it configurable! Thanks |
| Comment by Mark Benvenuto [ 13/Jan/17 ] |
|
These network messages are logged at informational, and there is no way to lower the log level today to below informational (i.e., only show warning, error and fatal log messages). These trace messages are critical for many customer support cases. |