Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-8071

Addition of 'originatingCommand' to getMore log messages & profiler entries

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • Server_Docs_20231030
    • None
    • Server
    • None

    Description

      For MongoDB 3.4

      Under SERVER-23260 we have added an "originatingCommand' field to getMore diagnostics. This field appears in slow diagnostic logging, the profiled getMore entries and in db.currentOP(). Please add definitions to our documentation for this field where appropriate.

      A rough definition for this field is: 'The command object that generated the cursor this getMore is executing against'.

      Sample log output:

      command profile_getmore.test command: getMore { getMore: 35432647810, collection: "test", batchSize: 2.0 } originatingCommand: { find: "test", filter: { a: { $gt: 0.0 } }, batchSize: 2.0, sort: { a: 1.0 } } cursorid:35432647810
      

      Sample profiler output:

       { "op" : "getmore", "ns" : "profile_getmore.test", "query" : { "getMore" : NumberLong("46013230076"), "collection" : "test", "batchSize" : 2 }, "originatingCommand" : { "find" : "test", "filter" : { "a" : { "$gt" : 0 } }, "batchSize" : 2, "sort" : { "a" : 1 } }, "cursorid" : 46013230076}
      

      A quick search for relevant pages brings me to the following:

      1. https://docs.mongodb.com/manual/reference/database-profiler/
      2. https://docs.mongodb.com/manual/reference/method/db.currentOp/#output-fields

      Attachments

        Activity

          People

            kevin.albertson@mongodb.com Kevin Albertson
            james.wahlin@mongodb.com James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              7 years, 36 weeks ago