Description
Fortimanager/FortiAnalyzer Debugger is a chrome extension that communicates with a Fortimanager or FortiAnalyzer via the Chrome extension API.
The goal of this extension is to improve the quality of GUI bug reports by collecting as much information as possible at the time of capture.
This avoids developers, QA, and TAC having to go back and forth multiple times to collect information throughout the debugging process.
Scope
This extension allows for capturing detailed debug information of a FortiManager/FortiAnalyzer's graphical user interface.
Requires FortiManager/FortiAnalyzer 6.4.0 GA or greater.
Solution
Download chrome extension from:
https://chrome.google.com/webstore/detail/fortimanagerfortianalyzer/dhdlbdcjpkjngafjclfegbbcajbfhlac
What is included on the tool?
Each Fortimanager/FortiAnalyzer debugger capture includes the following information:
- A video recording.
- Device meta information.
- Client and browser meta information.
- HTTP network logs.
- Various daemon debug logs.
- Javascript console logs.
- Device memory and CPU usage over time.
- Client memory and CPU usage over time.
Special note:
If the slowness issue is isolated to the GUI and the firmware version is 7.2.4 or above, it is recommended to check the apache mode used in the FortiManager under get system global. Before version 7.2.3, the default 'apache-mode' utilized the 'prefork' mode. However, as of version 7.2.4, the default configuration switches to the 'event' mode.
This change is aimed at supporting the HTTP/2.0 protocol. With HTTP/2.0, there is no limit on the maximum concurrency of HTTP requests, potentially leading to slower GUI performance if the client's environment imposes restrictions, whether they are network or implementation-related. HTTP/2 may face issues such as head-of-line blocking and resource prioritization, leading to slower performance compared to HTTP/1. Additionally, server push and intermediaries struggling with encrypted headers can further complicate matters. Implementing HTTP/2 requires more computational resources, which may affect response times. These complexities highlight scenarios where HTTP/1 might outperform HTTP/2.
If customers experience GUI slowness, the option is available to revert to the 'prefork' mode by using the following commands:
config system global
set apache-mode prefork
end
See the 7.2.4 release notes.
