Description
This article discusses logs that are not generated in the firewall.
Scope
FortiGate.
Solution
There are many instances where the logs do not generate.
Miglogd daemon is responsible for logging in to FortiGate.
To know the status of the logs, execute the below debug:
# diagnose debug application miglogd -1
# diagnose debug enable
# execute for 5 minutes
To disable the debug:
# dia deb dis
If the log has to be generated manually on the FGT for testing purposes, the below command can be used:
# diagnose log test
The above command will generate below log events:
-: an infected virus message with level - warning
-: a blocked virus message with level - warning
-: a URL block message with level - warning
-: a DLP message with level - warning
-: an IPS log message
-: an botnet log message
-: an anomaly log message
-: an application control IM message with level - information
-: an IPv6 application control IM message with level - information
-: deep application control logs with level - information
-: an antispam message with level - notification
-: a URL block message with level - warning
-: an ssh-command pass log with level - notification
-: an ssh-channel block with level - warning
-: an ssl-cert_blacklisted log with level - warning
