flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1502) Expose metrics to graphite, ganglia and JMX.
Date Wed, 17 Feb 2016 10:17:18 GMT

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

Stephan Ewen commented on FLINK-1502:

I agree with [~mxm], not all metrics should go to the JobManager. General TaskManager metrics
(JVM, memory, GC, ...) should be picked up from the TaskManager directly.

Some job-specific metrics should go to the JobManager (like for example numRecords/bytes,
size of state, number of spilled bytes, ...) for aggregation and display in the web frontend.

Would be nice if one could define for a metrics group whether it should be reported to the
JobManager or not.

> 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

View raw message