DescriptionFortiAnalyzer (FAZ) relies upon hcache tables to build
reports. If a report is not scheduled and autocache is not enabled, the
first run of the report will take extra time because the FAZ needs to
first build the required hcache tables. Pr...
This article covers a basic setup steps allowing FortiAnalyzer (FAZ) to
accept FortiClients (FCT) logs.FAZ collects FCT logs into FortiClient
ADOM. They logs are stored under the EMS's serial number managing the
FortiClients. And in order to do so th...
DescriptionThis article provides basic tips about creating custom
reports on a FortiGate (FGT). Most of the steps are available only in
the CLI. For more complicated custom report scenarios, Fortinet
recommends use of FortiAnalyzer (FAZ). FortiGate r...
DescriptionPrior to FortiOS v5.2.3, FortiGates only supported the use of
Windows Active Directory (AD) security groups under FSSO group filter
options.Starting with FortiOS firmware 5.2.3 and Collector Agent
v5.0.0229, FortiGates also support filteri...
DescriptionThis article describes the built in Time and Date macros in
FortiAnalyzer. SolutionMacros can be used on the FortiAnalyzer to fine
tune report output. Below is a list of macros which manipulate date and
time formatting:MacrosDescriptionExa...
Hi James, I think the slowness could be caused by the query scope send
from FGT to FAZ. In FGT 6.0.9 the the FGT sends limits 50 lines, while
FGT 6.2.3 sets limit 500 e.g: v6.0.9: Execute SQL query: SELECT * FROM
((SELECT ti1.*, ti2."devid",ti2."vd",...
it is better if you could opened a support ticket as somebody needs to
look at the FAZ and run some diagnostics.When you opened a ticket
provide following outputs to the support engineer:get sys statusdiag
fortilog logdiag log devicediag test app sql...
Please check if you have a valid subscription for Threat Detection
Service (IOC). (under System Settings) Likely your system is not
licensed and not beet updated.