Probe remote processes JVM statistics log

Idea ID 1668588

Probe remote processes JVM statistics log

Currently we don’t log anywhere the JVM statistics of the remote processes started by several discovery adapters. It’s difficult to tell how and what memory they consume and normally it’s a trial and error approach. The end result would be to have a better logging on remote process failures due to insufficient memory or to be able to allocate the proper memory to such processes.

We have the general jvm_statistics.log but only for the probe JVM.

In CP28 (QCCR1H119428 ) we alligned the OOTB JVM parameters to JRE8 (metaspace) but we never log the JVM statistics for the remote processes that can be started during normal discovery flows.

2 Comments
Micro Focus Contributor
Micro Focus Contributor
Status changed to: Waiting for Votes

The idea has received an initial review to ensure adherence to our idea submission and community guidelines. More information may be needed at this stage and we expect the community to help prioritize the idea with comments and voting.

Micro Focus Expert
Micro Focus Expert

Quite problematic if a remote process has memory spikes. The only alternative is to live monitor the memory usage of the process.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.