[SERVER-68314] Add priority queueing metrics to the ticketholder Created: 26/Jul/22 Updated: 29/Oct/23 Resolved: 14/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2935-Milestone2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-08-08, Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19 |
| Participants: |
| Description |
|
As part of the project, we want to have metrics in the priority ticketholder for the following items:
General metrics that reflect statistics about the entire ticketing system, ticket acquisition priority agnostic. Note: These metrics are the same format as the metrics in the existing ticketing system.
"lowPriority" and "normalPriority" and "immidiatePriority" sections will include fields that serve the same purpose as the general section, but are specific to ticket acquisition priority.
Note: Since no "High" priority operations will ever queue, the values for "addedToQueue", "removedFromQueue", "queueLength", and "canceled" will always be 0. These metrics will be added as a part of |
| Comments |
| Comment by Githook User [ 14/Sep/22 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |
| Comment by Bruce Lucas (Inactive) [ 29/Jul/22 ] |
|
Does this refer to serverStatus metrics that will show up in FTDC? If so can you please point to the design or summarize on this ticket? |