Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-68314

Add priority queueing metrics to the ticketholder

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Execution Team 2022-08-08, Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19

      As part of the project, we want to have metrics in the priority ticketholder for the following items:

      • When the feature is enabled, the following metrics are exposed under the "concurrentTransactions" serverStatus section (the existing system also reports metrics under the "concurrentTransactions" section)

      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. 

      • "out" 
      • "available" 
      • "totalTickets" 

      "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.

        • "addedToQueue"
        • "removedFromQueue"
        • "queueLength"
        • "startedProcessing"
        • "processing"
        • "finishedProcessing"
        • "totalTimeProcessing"
        • "canceled"
        • "totalTimeQueuedMicros"

      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 SERVER-67951

            Assignee:
            haley.connelly@mongodb.com Haley Connelly
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: