Add link to collect log files for analysis

Idea ID 1796076

Add link to collect log files for analysis

The OO log files capture performance details of the OO infrastructure.  Problems such as flow errors, worker crashes, slow performance, etc, often require the need to perform some in-depth troubleshooting. 

When Micro Focus support or R&D are engaged, they need to review the OO logs to begin identifying what the root cause of any error may be.

To help the customer and improve the support experience there should be a menu option in the Central UI for a user to 'Collect log files'. In one click a zip file could be created with the following files for the user to send to Micro Focus;

- wrapper.log

- execution.log

- general.log

- server.log

- VersionInfo.txt

Valued Contributor.
Valued Contributor.

This would be a significant time saver!

Super Contributor.. Super Contributor..
Super Contributor..

I completely agree!

Honored Contributor.. Honored Contributor..
Honored Contributor..

This would be fantastic

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

Sounds like a reasonable idea. I will change the status to Waiting for Votes but I have several questions.

Do you want to grab the current logs, or for a specific time period?

What about old logs? Every OO administrator is responsible to establish the retention policy for their logs. 

This can be achieved by a simple script. Do we really need a UI for this functionality?

Micro Focus Expert
Micro Focus Expert

The idea is about improving the user experience. Capturing the current log files is a good starting point should troubleshooting be required and using a button to grab these gives a good professional image for an automation tool like OO.

Honored Contributor.
Honored Contributor.

I agree.

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor


From R&D's point of view, collecting logs from UI is not something that is recommended to be implemented.

Consider having a cluster - which logs you want to collect? What if only for one node? What about RASes ? or Studio?  What about when Central services are stopped? Also , streaming gigabytes of logs via the tomcat webserver, to have them available for download in UI, will over-load the web-server unnecessarily.

R&D already has such a mini-tool written, that will collect all central, ras, studio logs from a given <OO_HOME> path. But it was offered to Support team so far . 

The tool is a jar that has to be run on the machine where you want to collect the logs and is invoked simply from command line , something like:

> java -jar log-collect.jar -h <OO_HOME> -t <target_folder>

This would create a zip of all logs and config files found under the given path.

Let us know if this solution is acceptable for your usage and if yes, we'll try to publish it somewhere for general availability.

Honored Contributor.
Honored Contributor.

In my opinion, having this tool is a good thing since it do what we want.

Micro Focus Expert
Micro Focus Expert

Thanks for your feedback.  Any tools and scripts for support are really useful.
The nature of this request however, is to give customers an easy way to gather logs through the GUI. This is intended to be a starting point for troubleshooting only and more detailed and specific analysis can be performed thereafter if required.  

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.