[SERVER-65716] "--quite" flag doesn't seem to do anything/still too verbose Created: 18/Apr/22 Updated: 27/Apr/22 Resolved: 27/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Callum Gare | Assignee: | Chris Kelly |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | The commands below show the latest version of mongod being run for 10 seconds before being quit then having the number of lines they emitted counted. Both produce 94 lines. callumgare@Meeka ~/r/porn-cache-new> docker run --rm --entrypoint=/usr/bin/timeout mongo:5.0.7 10 /usr/local/bin/docker-entrypoint.sh mongod | wc -l ``` |
| Participants: |
| Description |
|
As far as I can tell the "–quite" flag doesn't seem to make the logs any less verbose. When I spin up a new instance of the mongo docker image it produces a whole bunch of noise which makes it easy to mess logs which are actually important. |
| Comments |
| Comment by Chris Kelly [ 26/Apr/22 ] |
|
Hi Callum, Chances are that --quiet is working as intended, which is to say it is suppressing:
There is always going to be some amount of output from the process by design. During startup, the amount of output can be rather similar, and it appears normal based on the sizes you provided. However, your expectation for even less logging is understandable, and it sounds like it would be useful feature to others as well for only displaying critical events. May I please ask that you submit this same request at feedback.mongodb.com? Given that this is currently normal behavior, this would be considered more of a feature request. Regards, Christopher |