flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Renkai Ge (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4532) Allow independent metrics reporter for tasks
Date Wed, 31 Aug 2016 12:10:21 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452069#comment-15452069

Renkai Ge commented on FLINK-4532:

[~StephanEwen] So should I close this issue and create a new one for (1) or resolve this issue
by implement (1) and wait for others to complete (2)?

> Allow independent metrics reporter for tasks
> --------------------------------------------
>                 Key: FLINK-4532
>                 URL: https://issues.apache.org/jira/browse/FLINK-4532
>             Project: Flink
>          Issue Type: Improvement
>          Components: Metrics
>            Reporter: Renkai Ge
> Currently,  JobManager, TaskManager and Task share the same configuration of reporters,
and implementations of org.apache.flink.metrics.reporter.MetricReporter  should be in classpath
before JobManager started. 
> In a cluster with multi tenancy, cluster administrator may want to monitor the cluster
metrics in one place, and the owner of a application want to view the metrics of their application
in somewhere else, and they may put custom MetricReporter in the application jar if the classpath
don't provide one.
> I want to implement this by:
> 	1. Make it possible to load MetricReporter from userCodeClassLoader.
> 	2. Put new API into ExecutionConfig like {code}public long enableAdditionalMetricReporters(List<String>
classNames,boolean disableGlobalMetricReporters);{code}
> I will begin to work on this if you guys agrees.

This message was sent by Atlassian JIRA

View raw message