Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Query Execution
Description
"cursor" : {
|
"timedOut" : NumberLong(<num>),
|
"open" : {
|
"noTimeout" : NumberLong(<num>),
|
"pinned" : NumberLong(<num>),
|
"multiTarget" : NumberLong(<num>),
|
"singleTarget" : NumberLong(<num>),
|
"total" : NumberLong(<num>), } }
|
We'd like some way to distinguish client cursors from secondary cursors. Charlie suggested this could be accomplished by discounting oplog cursors while still including change streams. We will have some false negatives, but I expect this new field to be more representative of client activity than the current field.
Attachments
Issue Links
- is related to
-
SERVER-44735 track metrics for system initiated operations (commands, reads) separately from client initiated ones
-
- Backlog
-