-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Security
Currently, the minimum severity the shell logs is "info" by default (https://github.com/mongodb/mongo/blob/fc021de4af28a6171e0eea8f5311268c5491876a/src/mongo/shell/shell_options.cpp#L117-L122) while the server processes (mongod, s, q, etc) have "log" as the minimum severity they log by default (see https://github.com/mongodb/mongo/blob/fc021de4af28a6171e0eea8f5311268c5491876a/src/mongo/logv2/log_component_settings.cpp#L39).
Although they have the same logged message and output format (see https://jira.mongodb.org/browse/SERVER-49745), INFO and LOG are subtly different severities, so this distinction means that it is easy to accidentally log an important log line that shows up by default in servers but not in the shell - this happened with stacktraces in https://jira.mongodb.org/browse/SERVER-72582 . Can we consider making the shell and servers have the same default minimum log severity?
- related to
-
SERVER-72582 Ensure stacktraces are logged from the `mongo` shell
- Backlog
-
SERVER-49745 Subtle undocumented difference between LOGV2 and LOGV2_INFO.
- Closed