You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Neelesh Srinivas Salian (JIRA)" <ji...@apache.org> on 2017/04/17 17:52:41 UTC

[jira] [Commented] (FLINK-4831) Implement a log4j metric reporter

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

Neelesh Srinivas Salian commented on FLINK-4831:
------------------------------------------------

Shall I work on this if no one has begun already?

> Implement a log4j 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
>            Priority: Minor
>              Labels: easyfix, starter
>
> 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.3.15#6346)