You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2019/12/08 10:29:00 UTC
[jira] [Closed] (FLINK-14993) Pass all reporter-specific settings
via the FrontMetricGroup
[ https://issues.apache.org/jira/browse/FLINK-14993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-14993.
------------------------------------
Resolution: Fixed
master: 7d375cca5e3f95402c00b9ab95f6b76421b5e683
> Pass all reporter-specific settings via the FrontMetricGroup
> ------------------------------------------------------------
>
> Key: FLINK-14993
> URL: https://issues.apache.org/jira/browse/FLINK-14993
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> For the assembly of scopes there currently exist 3 parameters that are defined per reporter; the reporter index, used to cache scopes separately per reporter, and the delimiter/filter pair that is applied to each scope.
> Currently, the FrontMetricGroup only provides the index, which the AbstractMetricGroup uses to figure out which delimiter should be used.
> Instead we can store the delimiter directly in the FrontMetricGroup; this simplifies the metric group implementation and further decouples the scope generation from the MetricRegistry.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)