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

Report the same metrics in both "Slow query" and the profiler data documents

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • QI 2023-04-03, QI 2023-04-17, QI 2023-05-01, QI 2023-05-15, QI 2023-05-29, QI 2023-06-12, QI 2023-06-26, QI 2023-07-10, QI 2023-07-24, QI 2023-08-07

      It seems like an oversight that metrics have been added to one or the other of "Slow query" logs or the profiler data documents. They are both system diagnostic tools, and it seems like an unpleasant user experience (a surprise) that metrics would be available in one but not the other.

      OpDebug::report puts information into "Slow query" logs. Whereas it looks like OpDebug::append is leveraged by the profiler. Lastly there is a OpDebug::appendStaged function for creating a CurOp report filter (returns a lambda function) of the operations returned (added by SERVER-49102) used in ProfileFilter.

      A new metric must be added in three places to ensure it is included in both profiler (and filtered profiler) and "Slow query" results. These paths should be documented – there is none to inform developers where to add code – and merged as much as possible

            Assignee:
            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: