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

Query Instrumentation Support

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Execution

    Description

      Currently, there lacks visibility into the time a user-initiated command like find or update spends in different parts of the system and between mongos and mongod after being sent from the driver. To debug help tickets or identify performance bottlenecks in a command, a user may want to know the time spent by a query in index scans, disk access etc. It would be great if such a capability could be added to the commands in a way such that any new command implemented can use this instrumentation library to opt into instrumenting different parts of its execution lifecycle and the instrumentation metrics for existing commands can be fetched on turning instrumentation on.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            abdul.qadeer@mongodb.com Abdul Qadeer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: