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 2017/10/26 07:42:00 UTC
[jira] [Closed] (FLINK-4831) Implement a slf4j metric reporter
[ https://issues.apache.org/jira/browse/FLINK-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-4831.
-----------------------------------
Resolution: Fixed
1.4: c0199f5d181a8d249201004f6ec6f897f9b799c4
> Implement a slf4j metric reporter
> ---------------------------------
>
> Key: FLINK-4831
> URL: https://issues.apache.org/jira/browse/FLINK-4831
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
> Affects Versions: 1.1.2
> Reporter: Chesnay Schepler
> Assignee: Hai Zhou UTC+8
> Priority: Minor
> Labels: easyfix, starter
> Fix For: 1.4.0
>
>
> For debugging purpose it would be very useful to have a log4j metric reporter. If you don't want to setup a metric backend you currently have to rely on JMX, which a) works a bit differently than other reporters (for example it doesn't extend AbstractReporter) and b) makes it a bit tricky to analyze results as metrics are cleaned up once a job finishes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)