You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2017/11/01 12:27:01 UTC

[jira] [Created] (FLINK-7957) Add MetricGroup#getLogicalScope

Chesnay Schepler created FLINK-7957:
---------------------------------------

             Summary: Add MetricGroup#getLogicalScope
                 Key: FLINK-7957
                 URL: https://issues.apache.org/jira/browse/FLINK-7957
             Project: Flink
          Issue Type: Improvement
          Components: Metrics
    Affects Versions: 1.4.0
            Reporter: Chesnay Schepler
            Assignee: Chesnay Schepler
             Fix For: 1.4.0


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:

{code}
((FrontMetricGroup<AbstractMetricGroup<?>>)group).getLogicalScope(CHARACTER_FILTER, '.')
{code}

Given the wide-spread of this kind of scope i propose to move it into the MetricGroup interface.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)