[
https://issues.apache.org/jira/browse/METRON-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15808162#comment-15808162
]
ASF GitHub Bot commented on METRON-636:
---------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/incubator-metron/pull/400
I suppose a `df` or equivalent would be worthwhile. (Only report physical
volumes, or perhaps volumes > 5GB capacity.)
The other major limiter on performance / capacity is intra-cluster Ethernet
bandwidth. So that would be nice to report. But this can be tricky or
impossible to read, depending on the NIC hardware and BIOS support, and of
course whether you're on a physical machine or a VM. I don't really have any
guidance to offer, just a wish, if you have an idea of how to approach it.
> 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)
