[SERVER-41997] currentOp should show the hierarchy of commands being run when a command internally triggers another command Created: 28/Jun/19 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
currentOp currently return only the latest (current) operation being run and gives no evidence of the original command triggered by the user. For example, if I am running aggregation command with $out. The currentOp could return the command as renameCollection, createCollection or aggreation, based on which operation is being run currently. It doesn't have any 'parent' field which can show the parent operation. This means that, if a user wants to see if there are any agg operations. This is no accurate way to find out, since the results of currentOp are misleading. |