Investigate behavior of OpDebug mongot metrics if pipeline has multiple mongot stages

XMLWordPrintableJSON

    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We have a series of metrics on OpDebug that store mongot-related information (mongotCursorId, msWaitingForMongot, mongotBatchNum, mongotCountVal, mongotSlowQueryLog). If the pipeline has multiple mongot stages (like [$search, $unionWith: [$vectorSearch]]), both mongot stages may overwrite or combine their metrics. We should investigate the current behavior, document it better, and consider if we want to change that behavior.

            Assignee:
            Will Buerger
            Reporter:
            Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: