[SERVER-44866] Impossible to custom log verbosity to warning - log flooding Created: 27/Nov/19  Updated: 18/Dec/19  Resolved: 18/Dec/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: thomas jalabert Assignee: Eric Sedor
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-18339 Log only warning, error or fatal mess... Closed
Operating System: ALL
Participants:

 Comments   
Comment by Eric Sedor [ 18/Dec/19 ]

thomas_jalabert@hotmail.com,

I am going to close this as a duplicate of SERVER-18339. Hopefully, the quiet option is helpful for your use-case.

Sincerely,
Eric

Comment by Eric Sedor [ 02/Dec/19 ]

Hi thomas_jalabert@hotmail.com,

First, does quiet help or is this too restricting?

Second: Is there an aspect of your request that isn't covered at SERVER-18339?

Sincerely,
Eric

Comment by thomas jalabert [ 27/Nov/19 ]

Why allow only Information and Debug loglevel verbosity (from 0 to 5 as said here : https://docs.mongodb.com/manual/reference/log-messages/#verbosity-levels)

Could you add the possibility to choose other logLevel ? Every connection is loggued with Information loglevel...

 

Thanks

Related to https://jira.mongodb.org/browse/SERVER-18339

 

Generated at Thu Feb 08 05:07:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.