[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7957:
----------------------------------
Labels: auto-unassigned stale-minor (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add MetricGroup#getLogicalScope
> -------------------------------
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Affects Versions: 1.4.0
> Reporter: Chesnay Schepler
> Priority: Minor
> Labels: auto-unassigned, stale-minor
>
> 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.3.4#803005)
