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

db.setProfilingLevel(2) doesn't log what was inserted

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 2.0.0
    • Component/s: Usability
    • Labels:
    • Environment:
      OS X 10.7, MongoDB 2.0, though it did the same on 1.8
    • ALL

      > use profilingtest
      switched to db profilingtest
      > db.setProfilingLevel(2);

      { "was" : 0, "slowms" : 100, "ok" : 1 }

      > db.getProfilingLevel()
      2
      > db.somecollection.insert(

      {cheese: true}

      )
      > db.somecollection.findOne()

      { "_id" : ObjectId("4e7084af0c324c44055b5180"), "cheese" : true }

      > db.system.profile.find()
      { "ts" : ISODate("2011-09-14T10:40:23.391Z"), "info" : "query profilingtest.$cmd ntoreturn:1 command:

      { profile: -1.0 }

      reslen:74 bytes:58", "millis" : 0 }

      { "ts" : ISODate("2011-09-14T10:40:47.091Z"), "info" : "insert profilingtest.somecollection", "millis" : 2 }

      { "ts" : ISODate("2011-09-14T10:40:54.220Z"), "info" : "query profilingtest.somecollection ntoreturn:1 reslen:67 nscanned:1 \nquery: {} nreturned:1 bytes:51", "millis" : 0 }

            Assignee:
            Unassigned Unassigned
            Reporter:
            russell.smith@ukd1.co.uk Russell Smith
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: