[SERVER-85449] Differentiate oplog operations in serverStatus query metrics Created: 19/Jan/24 Updated: 30/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Change streams, Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Chris Harris | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | query-product-scope-1, query-product-urgency-1, query-product-value-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
Presently operations against the oplog (eg Change Streams) increment various serverStatus metrics such as queryExecutor.scannedObjects and document.returned. We should separate out reporting of this work into its own metric so that downstream consumers can better attribute the sources. Bonus points if we can further differentiate between internal and external callers for the oplog operations. Note: if queryExecutor.scanned or other metrics are also incremented by these operations then those should be included in this change as well. |