[
https://issues.apache.org/jira/browse/FLINK-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16159094#comment-16159094
]
ASF GitHub Bot commented on FLINK-4831:
---------------------------------------
GitHub user yew1eb opened a pull request:
https://github.com/apache/flink/pull/4661
[FLINK-4831] Implement a slf4j metric reporter
## What is the purpose of the change
Implement a slf4j metric reporter For debugging.
## Brief change log
## Verifying this change
- *Added unit test Slf4jReporterTest*
- *Build a local flink cluster test Slf4jReporter, it works well*
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (no)
- The serializers: (no)
- The runtime per-record code paths (performance sensitive): (no)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
## Documentation
- Does this pull request introduce a new feature? (yes)
- If yes, how is the feature documented? (docs)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yew1eb/flink FLINK-4831
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4661.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4661
----
commit 79804a6ae554b93d41e5c8748c6442c2aa330fa2
Author: yew1eb <yew...@gmail.com>
Date: 2017-09-06T15:09:13Z
Implement a slf4j metric reporter
----
> 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
> 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.4.14#64029)
