LDAPOperationStats are not included in profiler entries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Security
    • ALL
    • Server Security 2026-06-19
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This block attempts to add LDAPOperationStats to the profiler entry, but the BSONObjectBuilder is being created incorrectly - it should be initialized with a call to subobjStart on the parent BSONObjectBuilder.

      Also, this block for generating the bson that the profile filter uses adds both LDAPOperationStats and UserCacheAccessStats as separate nested objects but with the same field name, which looks unintentional. They likely should be "authorization" and "LDAPOperations" like in report().

      It doesn't look like we have any tests checking these fields in slow query log or profiler output, so it could be good to add that here.

            Assignee:
            Karen Zhao
            Reporter:
            Alyssa Clark (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: