Known Issues
The following issues have been identified in FortiAnalyzer version 7.4.3. To inquire about a particular bug or to report a bug, please contact Fortinet Customer Service & Support.
Fabric View
Bug ID | Description |
---|---|
918006 |
An issue with the EMS Asset Inventory has been identified. When running the playbook, no assets or inventory are displayed on FortiAnalyzer, and the Fabric View lists remain empty. |
FortiView
Bug ID | Description |
---|---|
954542 | When the time range is extensive, FortiAnalyzer may experience limitations in handling data points, resulting in potential omissions of data entries in the final results for FortiView > SD-WAN Monitors widgets. |
989446 |
FortiView SD-WAN Bandwidth Overview displays no data. |
Log View
Bug ID | Description |
---|---|
1020783 |
Log View may occasionally display "No record found" instead of logs, especially when users attempt to navigate to additional pages. |
Others
Bug ID | Description |
---|---|
817639 | FortiAnalyzer archive logs caused unexpected increase in the disk quota usage. |
1047184 |
When the "Allow FortiToken Mobile push notification" policy is enabled in the FortiAuthenticator, the "Token Code" field is not displayed on the FortiAnalyzer's GUI login page for manual insertion of the token. It should be noted, the token is received on the phone, and the login completes successfully. |
1062128 |
After upgrading to the latest available build, the FortiAnalyzer GUI displays the warning message: "A new firmware version is available". |
Reports
Bug ID | Description |
---|---|
895106 | Top destination by bandwidth dataset does not exclude long-live session. |
937700 |
Source IP on the Report is shown as the Victim in the default Security Analysis report. |
System Settings
Bug ID | Description |
---|---|
766197 | An admin user limited to a device group can view all device's log |
1027547 |
In certain cases (currently under investigation), the License Status on FortiAnalyzer may be incorrectly displayed as "Expired" despite the license being active in the account. Workaround: Restart the FortiAnalyzer when feasible. |