track metrics for system initiated operations (commands, reads) separately from client initiated ones

XMLWordPrintableJSON

    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently serverStatus splits some operations to allow tracking them separate if they are internally triggered but not all.  For instance deletes from TTL thread are tracked separately from "regular" deletes initiated by client.

      It would be useful to do the same for reads, getMores and commands initiated by system, like secondaries reading the oplog, automation agent running commands, etc.

              Assignee:
              [DO NOT USE] Backlog - Query Optimization
              Reporter:
              Asya Kamsky
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: