The following issues have been identified in FortiAnalyzer version 6.2.6. For inquires about a particular bug or to report a bug, please contact Fortinet Customer Service & Support.
Device Manager view may show
red icons for VDOMs even when the log is received.
||SNMP alert is not generated for
event handler triggered by FortiWeb attack logs.
||FortiAnalyzer may prompt empty
SOC website related to dashboard while the web filter logs exist.
||There may be bandwidth
discrepancy under FortiView > Application & websites > Top
||FortiAnalyzer should hide
Device and Time Frame selection in FortivView Threat Map.
Bandwidth may not match between
FortiAnalyzer and FortiGate.
||The selected time range may not correspond with the time range in the charts for the Resource Usage drilldown.
Incident of Compromised Hosts
may not be triggered.
||FortiView monitor WiFi widget
is not showing Bridged SSID information.
||The GUI many not respond when navigating to Monitors >
Local System Performance.
||Some graphs may not render data
||Downloading log files from Log
View or Browse are not exported in the correct CSV format.
||The remote IP for SSL-VPN is
showing as IPsec Remote IP.
||Hiding column(s) in Log View
may cause the filters to reference the wrong column.
Some IPS archive files only contain the
BODY instead of showing the entire Attack Context .
||FortiAnalyzer may not display
Traffic Logs in Log View and return Web Server Error 500.
||When two filters are defined
and the first filter is removed, clicking on the remaining filter may
reference the filter that was removed.
||After creating an ADOM for
FortiMail, the ADOM is not visible on the GUI and mail domain logs are not going
to the default FortiMail ADOM.
||Actual analytic logs do not
match what is observed in Log View.
Log View may load infinitely with
Custom Time Period.
||Downloading an uncompressed CSV
format log prompts web server error 500.
||Changing the value for
system.global.enc-algorithm is not applied to oftpd until a reboot.
||File parser may keep crashing
every few minutes.
||FortiAnalyzer may consume high
disk I/O resource and high throughput may cause high CPU usage.
||FortiAnalyzer may consume high usage
on I/O resources every hour due to fazwatch.
||FortiAnalyzer may not be able
to generate the SaaS Application Usage Report with
Obfuscate User feature.
||FortiAnalyzer is not generating
all local Event logs for reports.
||After upgrade, all default
reports and event handler lists are lost.
||The pre-defined reports items
should be created in the new ADOM even if the same name being re-used.
||Scheduled report does not run
if the report owner has been deleted from the admin list.
||SD-WAN reporting graphs default
to a scale of one second where the scale should auto-scale to milliseconds.
||Free text filter does not work
when using (~) tilde sign on syslog ADOM for the msg field.
||ADOMs may disappear randomly
from ADOM configuration while editing it.
||FortiAnalyzer may not apply
Not equal to operator when Log Forwarding > Log
Filter is configured with the GUI.
CEF log forwarding start time
does not match with event time.