[
https://issues.apache.org/jira/browse/METRON-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798833#comment-15798833
]
ASF GitHub Bot commented on METRON-636:
---------------------------------------
Github user anandsubbu commented on the issue:
https://github.com/apache/incubator-metron/pull/400
Hi @nickwallen , thank you for the review.
At the outset, getting the system CPU and Memory info would help
troubleshooting, especially for single node deployments which are attempted on
environments with scarce resources (This
[thread](https://community.hortonworks.com/questions/51666/apache-metron-single-node-installation-problems.html)
for example).
My intention is in fact to capture the 'static' system information. I agree
with the challenges associated with capturing the runtime information--which
this script is not intended to do.
My initial approach was to dump the contents of `/proc/cpuinfo` and
`/proc/meminfo`. However, for lack of the same equivalent on Mac, I resorted to
getting the first few lines of `top` (again with different switches for Linux
and Mac :/).
I can still dump the output of /proc/cpuinfo and /proc/meminfo on Linux and
use a different alternative for Mac. I looked as much but could not find one
for Mac. Please let me know if you are aware of one.
> 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)
