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

Matthew Clarke commented on NIFI-1462:
--------------------------------------

I think the above information once collected should also be presented in the 
NiFi UI.  My thought would be to make this info accessible through the "about" 
link.  Clicking about brings up the existing pop-up that provides the running 
NiFi version, but also provides via an embedded link or second tab the above 
system information.

If possible, i would include number of CPU cores and system memory.  Knowing 
this additional information can help us optimize there NiFi.  (i.e - Over 
allocation of threads on processors, Available space to increase Heap, or heap 
set to high base don system available resources)

We don't want to assume those deploying the app know how to get all this 
information from the system it is running on. Knowing all this information can 
help with tuning NiFi. Just my two cents. 

> NiFi should log environment information on startup
> --------------------------------------------------
>
>                 Key: NIFI-1462
>                 URL: https://issues.apache.org/jira/browse/NIFI-1462
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Mark Payne
>
> When users have questions on the dev@ and users@ mailing lists, quite often 
> the first response they receive is to request information about which 
> operating system they are running, max heap size, etc. NiFi should log all of 
> this information on startup, so that it is all very easily gathered.
> Things to include:
> * Operating System (name & version)
> * Java Vendor
> * Java Version
> * Min Heap Size
> * Max Heap Size
> * Garbage Collector
> * Max # of open files for user
> * Max # of processes for user
> These may not all make sense for all operating systems / environments but the 
> info should be gathered when it does make sense.



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

Reply via email to