[SERVER-20925] Consider adding opCommand metadata to OpDebug Created: 14/Oct/15 Updated: 12/Jul/17 Resolved: 09/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 3.1.9 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Log level 1 is commonly used to capture the details of all messages processed by a mongod. It would make sense to also include the metadata portion of the request as well. |
| Comments |
| Comment by Mathias Stearn [ 09/Jun/17 ] |
|
The transition to OP_MSG means that we no longer have metadata. These fields are now just part of the body. |
| Comment by Scott Hernandez (Inactive) [ 14/Oct/15 ] |
|
Should this also be included for currentOp output as well? |