Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
None
-
Fully Compatible
-
Query 2019-05-20, Query 2019-06-03
Description
Log mongot cursor IDs so users can trace operations between mongod and mongot.
The intent here is to give users a way to correlate diagnostic logs by operation between mongod and mongot. Here is an example of what that might look like:
2019-04-01T10:22:32.285-0700 I COMMAND [conn9] command foo.bar appName: "MongoDB Shell" command: aggregate { aggregate: "bar", pipeline: [ { $fts: { term: { name: "evan" } } } ], cursor: {}, mongotCursor: { ok: 1, id: 5613672040878147038, fetchMs: 55 } ... $db: "foo" } numYields:0 ok:1 ... protocol:op_msg 112ms
|
Attachments
Issue Links
- related to
-
SERVER-40417 Log time spent waiting for mongot
-
- Closed
-