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

ASF GitHub Bot commented on METRON-636:
---------------------------------------

GitHub user anandsubbu opened a pull request:

    https://github.com/apache/incubator-metron/pull/400

    METRON-636: Capture memory and cpu details as a part of platform-info…

    … script
    
    Added top commands for Linux and Mac to be captured as a part of the 
platform-info.sh script.

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

    $ git pull https://github.com/anandsubbu/incubator-metron METRON-636

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

    https://github.com/apache/incubator-metron/pull/400.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 #400
    
----
commit c5b9168740308a65f74229f2fde650138a675173
Author: Anand Subramanian <[email protected]>
Date:   2016-12-21T08:21:51Z

    METRON-636: Capture memory and cpu details as a part of platform-info script

----


> Capture memory and cpu details as a part of platform-info script
> ----------------------------------------------------------------
>
>                 Key: METRON-636
>                 URL: https://issues.apache.org/jira/browse/METRON-636
>             Project: Metron
>          Issue Type: Improvement
>    Affects Versions: 0.3.0
>            Reporter: Anand Subramanian
>            Assignee: Anand Subramanian
>            Priority: Minor
>
> The platform-info.sh script currently does not capture the system memory 
> footprints.
> Many issues reported by users when deploying quick dev or full dev single 
> node deployments are due to system constraints (low memory for e.g.). It 
> would be good to enhance the platform-info script so that it can ease out 
> finding potential resource issues.



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

Reply via email to