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

Log mongot cursor id and time spent blocked waiting for mongot

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.12
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Epic Link:
    • Sprint:
      Query 2019-05-20, Query 2019-06-03

      Description

      Log mongot cursor IDs so users can trace operations between mongod and mongot.

      The intent here is to give users a way to correlate diagnostic logs by operation between mongod and mongot. Here is an example of what that might look like:

      2019-04-01T10:22:32.285-0700 I  COMMAND  [conn9] command foo.bar appName: "MongoDB Shell" command: aggregate { aggregate: "bar", pipeline: [ { $fts: { term: { name: "evan" } } } ], cursor: {}, mongotCursor: { ok: 1, id: 5613672040878147038, fetchMs: 55 } ... $db: "foo" } numYields:0 ok:1 ... protocol:op_msg 112ms
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ted.tuckman Ted Tuckman
              Reporter:
              david.storch David Storch
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: