[SERVER-61763] Add query related metrics to serverStatus & currentOp Created: 29/Nov/21 Updated: 12/Aug/22 Resolved: 12/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2022-01-24, Execution Team 2022-06-27, Execution Team 2022-08-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Project task placeholder. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 12/Aug/22 ] |
|
I've filed SERVER-68806 to look into generally setting the read timestamp on currentOp, whenever we have one. And I've filed I don't think there's anything further that would be useful to add, that I can currently think of. Resolving. |
| Comment by Dianna Hohensee (Inactive) [ 12/Aug/22 ] |
|
I realize that a lot of read concerns aren't going to specify a timestamp at which to read, in which case this won't be helpful. |
| Comment by Dianna Hohensee (Inactive) [ 11/Aug/22 ] |
|
I made a pass through the design document suggestions/proposals for metrics. What we do not yet track, and still seem worthwhile adds, are the following: CurrentOp additions:
|