I can only see data in reports for process set elements in eHeatlh. This represents the aggregated data points for all system processes contained within the process set. Sometimes it is useful to examine this data on a process by process basis.
Is there any way to gather and expose data for individual system process elements in reports, instead of the aggregated process set element data?
Can eHealth be configured to report on individual system process elements instead of on just the aggregated process set elements?
Yes, this is possible in eHealth and is done via environment variable configuration changes on the server.
The environment variable that is used to change this configuration is:
Per the "eHealth Command and Envirnment Variables Reference Guide" this variable is defined as:
- Enables storing and reporting of statistics for individual system process elements (as opposed to aggregate process set elements).
- To enable CA eHealth to report on new process elements, set this variable to yes before you discover the new elements.
- Possible values and their meaning:
- yes: CA eHealth discovers and stores data for system process elements. You can then run reports for those process elements.
- no: Disables the storing of polled statistics for individual process elements in the CA eHealth database; however, CA eHealth still discovers them.
- Default: no
- Note that setting this to yes does not change the data collection for the already existing process set elements. The aggregated statistical data presented by those elements will continue to be gathered and available for reporting purposes.
To enable eHealth to report on new process elements, set this variable to yes before you discover the new elements. This will automatically check "Record Detailed Data" for process elements at discovery time.
In Windows systems, after setting the new environment variable value, restart the eHealth service in order to have the new value acknowledged by the software. In Windows we can try either:
- Restart the eHealth63 Service via the Services UI
- In the command line as the $NH_USER, run "nhServer stop" followed by "nhServer start"
In Unix systems, we just need to restart the web server for the change to take affect. As the user root run: