[SERVER-62658] Operation resource consumption metrics don't account for clustered collection key size Created: 14/Jan/22 Updated: 29/Oct/23 Resolved: 24/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Jordi Olivares Provencio |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Minor Change | ||||
| Sprint: | Execution Team 2022-01-24, Execution Team 2022-02-07 | ||||
| Participants: | |||||
| Description |
|
We should probably include the cluster key size in the read/write accounting for operation resource consumption metrics, as we do not today. |
| Comments |
| Comment by Githook User [ 21/Jan/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |