[
https://issues.apache.org/jira/browse/FLINK-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152895#comment-15152895
]
Jamie Grier commented on FLINK-1502:
------------------------------------
I'm suggesting that we use Dropwizard Metrics library and expose those metrics
via JMX at a minimum/default, but also via optional configuration we could let
user's report metrics via any of the Metrics library's available metrics
Reporter classes. Ganglia and Graphite are both supported via the built-in
GangliaReporter and GraphitesReporter, but there are integrations with other
systems as well. Of particular interest to people running in production would
be StatsD, Librato, InfluxDB, etc.
https://dropwizard.github.io/metrics/3.1.0/manual/third-party/
What I'm suggesting is that we should expose the ability for people to
choose/configure which Reporters to use, but we should default to JMX. Many
3rd party tools will be able to consume/route these metrics if they're
available via JMX so that should be the default.
> 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)
