Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-35035

Additional levels of command debugging

    XMLWordPrintable

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Logging

    Description

      Even at level "1" of debugging, which is the lowest enabled debug level, the logs are pretty detailed:

      2018-05-16T18:05:34.876-0700 I COMMAND [conn2] command test.user appName: "MongoDB Shell" command: find { find: "user", filter: { email: "test@aol.com" }, $db: "test" } planSummary: EOF keysExamined:0 docsExamined:0 cursorExhausted:1 numYields:0 nreturned:0 reslen:82 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount:{ r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_msg 0ms
      

      It would be helpful to add another level which is perhaps a bit less detailed so that we don't fill our logs so quickly trying to debug what commands are being sent to our server:

      2018-05-16T18:05:34.876-0700 I COMMAND [conn2] command test.user command: find 
      

      Attachments

        Issue Links

          Activity

            People

              backlog-server-security Backlog - Security Team
              chengas123 Ben McCann
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated: