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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Minor - P4
    • 4.1.2
    • Affects Version/s: None
    • Component/s: Logging, Querying
    • None
    • Fully Compatible
    • Query 2018-07-16, Query 2018-07-30, Query 2018-08-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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".

            Assignee:
            Haley Connelly
            Reporter:
            Shakir Sadikali
            Votes:
            3 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: