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

ASF GitHub Bot commented on FLINK-3170:
---------------------------------------

GitHub user mxm opened a pull request:

    https://github.com/apache/flink/pull/1452

    [FLINK-3170] expose task manager metrics via JMX

    We can still change how we expose data via JMX. This is just a very simple 
approach. We could, for instance, expose all data via individual attributes.
    
    Here is a screenshot from `jconsole`:
    
    ![screen shot 2015-12-14 at 17 43 
16](https://cloud.githubusercontent.com/assets/837221/11788457/5e25a07a-a291-11e5-96e8-6a3674bf52f5.png)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mxm/flink FLINK-3170

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1452.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 #1452
    
----
commit e3a38349681fa5344b5ccb5058358e4b1283895b
Author: Maximilian Michels <[email protected]>
Date:   2015-12-13T12:44:18Z

    [FLINK-3170] expose task manager metrics via JMX

----


> Expose task manager metrics via JMX
> -----------------------------------
>
>                 Key: FLINK-3170
>                 URL: https://issues.apache.org/jira/browse/FLINK-3170
>             Project: Flink
>          Issue Type: New Feature
>          Components: JobManager
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> Java Management Extensions (JMX) may be used to publish task manager metrics. 
> Therefore, we need to define Bean interfaces to expose data and register 
> classes which implement these interfaces with the Bean Management Server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to