Add operationId to events and log messages

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Fixed
    • Priority: Unknown
    • 4.10.0
    • Affects Version/s: None
    • Component/s: Logging, Monitoring
    • None
    • None
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      See https://github.com/mongodb/specifications/blob/e9b4c96f3ff9b639c61feb7ed149ed14b59aabb6/source/command-logging-and-monitoring/command-logging-and-monitoring.rst#common-fields

      The lack of support for operationId makes it difficult to correlate events and log messages for 

      • connection check out started and connection check out completed/failed
      • bulk writes
      • cursor iteration 

      So there is no way to reliably determine, for example, how long an operation spent in a connection pool's wait queue.

              Assignee:
              Jeffrey Yemin
              Reporter:
              Jeffrey Yemin
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: