You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Weijie Guo (Jira)" <ji...@apache.org> on 2023/12/05 06:45:00 UTC
[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[ https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weijie Guo updated FLINK-7957:
------------------------------
Labels: 2.0-related auto-deprioritized-minor auto-unassigned (was: auto-deprioritized-minor auto-unassigned)
> 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
>
> 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)