Refactor ticket holder metrics to support new subclasses

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Metrics collection for TicketHolder subclasses are currently structured to make it easier to collect metrics for the relatively complex case of the PriorityTicketHolder, which wants to report metrics for three virtual queues it maintains. This makes it harder to introduce metrics for a new subclass. This ticket covers reimagining metrics collection for TicketHolders (and the related AdmissionContext), optionally reducing the number of atomics used in the process.

              Assignee:
              Matt Broadstone
              Reporter:
              Matt Broadstone
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: