Technical Tip: How to catch debug logs of GUI errors

[mbenvenuti]

Description	This document describes how to catch debug logs of GUI errors.
Scope	FortiSIEM.
Solution	Steps to follow:  Activate debug logs from super CLI as root: cp /opt/phoenix/config/log4j2.xml /opt/phoenix/config/log4j2.xml_bak sed -i 's/<Logger name=\"com.ph.phoenix\" level=\"info\" additivity=\"false\">/<Logger name=\"com.ph.phoenix\" level=\"debug\" additivity=\"false\">/' /opt/phoenix/config/log4j2.xml Access the FortiSIEM with Chrome web browser in private mode: Press F12 to display the developer tool Select the 'Network' section and 'record network logs' (the icon must be red to record). On the FortiSIEM web page, reproduce the issue and note the time of the test. In 'developer tool', select the 'Export HAR' file and attach this file to the ticket. Deactivate debug logs from the super CLI as root: mv /opt/phoenix/config/log4j2.xml_bak /opt/phoenix/config/log4j2.xml Capture the logs from super CLI as root: phziplogs /tmp/logs 1 Provide the .har file and the /tmp/logs from super to the support team.