[SERVER-59192] Command level log verbosity configuration Created: 09/Aug/21  Updated: 09/Aug/21

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

Type: New Feature Priority: Major - P3
Reporter: Alex Bevilacqua Assignee: Salman Baset
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Security 2021-08-23
Participants:

 Description   

Debugging commands occasionally requires increased verbosity, however increasing this at the node level can generate a lot of noise. This feature would allow any command to accept an optional logLevel parameter, similar to how comments were added to all commands via SERVER-29794.

Changing the log level can only be done via the logComponentVerbosity or logLevel server parameters, which are unavailable in managed environments (ex: MongoDB Atlas).

For example:

db.runCommand({
    find: "foo",
    filter: { bar: { $exists: true } },
    logLevel: {
      verbosity: <int>,
      <component1>: { verbosity: <int> },
      <component2>: {
        verbosity: <int>,
        <component3>: { verbosity: <int> }
      },
      ...
    }
    batchSize: 1000
});


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