[
https://issues.apache.org/jira/browse/FLINK-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288895#comment-15288895
]
ASF GitHub Bot commented on FLINK-1502:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1947#issuecomment-220014866
Few followups are actually needed before merging this:
1. We need to remove the example metrics
2. Conflicting metrics names should not result in failures. Metrics are
tooling, and problems in the tooling should not fail the core programs.
3. I think we should limit the available metrics types to Gauge and
Counter for now. I looked at Timers, Meters, and Histograms - they are very
high overhead each. As a follow-up, I would like to see if we can construct
simple Meters as views over counters. That way, the runtime code as no overhead
for the metering (it just maintains counters and gauges) and the registry code
needs to turn them into Meters asynchronously.
> 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: Chesnay Schepler
> 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)
