Idea ID: 1796076

Add link to collect log files for analysis

Status : Under Consideration
Under Consideration
See status update history
over 2 years ago

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

Labels:

OO - Platform
Parents
  • Hello, 

    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.

Comment
  • Hello, 

    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.

Children
No Data