Details
-
Sub-task
-
Status: Open
-
Not a Priority
-
Resolution: Unresolved
-
1.4.0
Description
Various reporters make use of a generalized scope string (e.g. "taskmanager.job.task.<metricname>"). This string can be generated with AbstractMetricGroup#getLogicalScope, which is however an internal API. As a result, the access pattern currently looks like this:
((FrontMetricGroup<AbstractMetricGroup<?>>)group).getLogicalScope(CHARACTER_FILTER, '.')
Given the wide-spread of this kind of scope i propose to move it into the MetricGroup interface.