[
https://issues.apache.org/jira/browse/FLINK-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142628#comment-15142628
]
Dongwon Kim commented on FLINK-1502:
------------------------------------
[~mxm] Could you elaborate more on the above explanation? is it about exposing
accumulators along with metrics? :-)
[~StephanEwen] Thank you! I'm trying to figure out this issue ;-) I'm also
looking at how Samza as you said.
I plan to use https://github.com/dropwizard/metrics as this library already
supports various reporters such as ConsoleReporter, JmxReporter,
GangliaReporter, and GraphiteReporter.
It looks desirable as TaskManager already uses the metrics library to create
the registry of metrics and sends them to JobManager.
For monitoring system like Ganglia, I plan to take an approach shown in my blog
post:
http://eastcirclek.blogspot.kr/2015/10/Collecting-JVM-metrics-to-Ganglia-using-io.dropwizard.metrics.html
Metrics like GC counts from JMX are ever growing so Ganglia graphs for such
metrics will have a very long y-axis when task managers are running for few
days.
For the reason, I plan to report to Ganglia only difference from the previously
known value of such metrics.
> Expose metrics to graphite, ganglia and JMX.
> --------------------------------------------
>
> Key: FLINK-1502
> URL: https://issues.apache.org/jira/browse/FLINK-1502
> Project: Flink
> Issue Type: Sub-task
> Components: JobManager, TaskManager
> Affects Versions: 0.9
> Reporter: Robert Metzger
> Assignee: Dongwon Kim
> Priority: Minor
> Fix For: pre-apache
>
>
> The metrics library allows to expose collected metrics easily to other
> systems such as graphite, ganglia or Java's JVM (VisualVM).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
