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/04/17 08:01:00 UTC

[jira] [Closed] (FLINK-11923) Move reporter setup out of MetricRegistry

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

Chesnay Schepler closed FLINK-11923.
------------------------------------
    Resolution: Fixed

master: 6f78a943ed626e4c232e9a706b9debf594c67ebd

> Move reporter setup out of MetricRegistry
> -----------------------------------------
>
>                 Key: FLINK-11923
>                 URL: https://issues.apache.org/jira/browse/FLINK-11923
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> {{MetricReporters}} are currently instantiated in the constructor of the {{MetricRegistryImpl,}} based on the reporter-specific {{Configuration}} provided by the {{MetricRegistryConfiguration}}. To ease testing it would be great if reporters are instead passed into the MetricRegistry instead, so that a reporter can be setup without having to go through the configuration every time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)