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

Expose query plan cache key in system.profile entry and query log lines

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.2
    • Component/s: Logging, Querying
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Query 2018-07-16, Query 2018-07-30, Query 2018-08-13
    • Case:

      Description

      It would be nice if we included a hash of all queries (without their binds) so we can get a sense for unique types of queries being run on a system and to be able to get a better performance profile for "bad" queries. If we could add that hash into the mongod.log we can easily "group" queries for prioritization when telling the customer what to "tweak".

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              haley.connelly Haley Connelly
              Reporter:
              shakir.sadikali Shakir Sadikali
              Participants:
              Votes:
              3 Vote for this issue
              Watchers:
              14 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: