Refactor server status metrics to colocate multiplanner and CBR metrics

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently there are server status metrics for multiplanner under metrics.query.multiPlanner, for CBR under metrics.query.CBR, and for subplanner under metrics.query.subPlanner. There are some shared metrics under metrics.query.planning

      We should refactor all individual planner metrics to be under the planning section, eg. metrics.query.planning.multiPlanner, metrics.query.planning.CBR, etc.

      Also, we should rename metrics like multiPlanner.classicCount, multiPlanner.classicMicros (and all CBR/subplanner equivalents) to be more descriptive of what is being tracked.

      Note that these changes will affect data warehouse queries.

      (example of where some metrics are, there are many other locations)

            Assignee:
            Unassigned
            Reporter:
            Natalie Hill
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: