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

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

GitHub user bhatsachin opened a pull request:

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

    [FLINK-1792] TM Monitoring: CPU utilization, hide graphs by default and 
show summary only

    Added CPU Load %, show/hide button for detailed graph and summary for the 
metrics

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

    $ git pull https://github.com/bhatsachin/flink dev-bhatsachin-flink-1792

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

    https://github.com/apache/flink/pull/553.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 #553
    
----
commit 5f5f6a9156a8bbe7dc98a998ade7dc0eab9b2912
Author: bhatsachin <bhats...@gmail.com>
Date:   2015-03-31T08:18:08Z

    [FLINK-1792] Add processCPULoad in metricsRegistry, add button to
    show/hide graphs, add summary for metrics

----


> Improve TM Monitoring: CPU utilization, hide graphs by default and show 
> summary only
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-1792
>                 URL: https://issues.apache.org/jira/browse/FLINK-1792
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Webfrontend
>    Affects Versions: 0.9
>            Reporter: Robert Metzger
>            Assignee: Sachin Bhat
>
> As per https://github.com/apache/flink/pull/421 from FLINK-1501, there are 
> some enhancements to the current monitoring required
> - Get the CPU utilization in % from each TaskManager process
> - Remove the metrics graph from the overview and only show the current stats 
> as numbers (cpu load, heap utilization) and add a button to enable the 
> detailed graph.



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

Reply via email to