Idea #23776
Allow users more control of MetricPlugin behavior
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/18/2019
Due date:
% Done:
0%
Estimated time:
Experiment:
DUNE
Description
MetricPlugin currently handles metric aggregation on behalf of the implementation plugins, which are only responsible for routing aggregated metrics to their destinations. There is a use-case, however, for plugin types which do their own aggregation or processing on the minimally-aggregated metrics coming directly from MetricManager.
To this end, I propose renaming the current MetricPlugin to something like "AggregatingMetricPlugin" and adding a pure virtual MetricPlugin interface which defines the minimal set of functions needed by MetricManager to pass metrics down. All current _metric plugins would then inherit from AggregatingMetricPlugin.