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

["Xintong Song (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xintong Song updated FLINK-7957:
--------------------------------
    Parent Issue: FLINK-36200  (was: FLINK-32378)

> Add MetricGroup#getLogicalScope
> -------------------------------
>
>                 Key: FLINK-7957
>                 URL: https://issues.apache.org/jira/browse/FLINK-7957
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Metrics
>    Affects Versions: 1.4.0
>            Reporter: Chesnay Schepler
>            Priority: Not a Priority
>              Labels: 2.0-related, auto-deprioritized-minor, auto-unassigned
>             Fix For: 3.0.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
(v8.20.10#820010)