Disk Logging
Only certain FortiGate models support Disk Logging (see above).
To enable Disk Logging, go to Log & Report > Log Settings, and select the checkbox next to Disk and apply the change. Some devices will require disk logging to be enabled in the CLI, using the following command:
config log disk setting set status enable
end
Configuration Dependencies
Most FortiView consoles require the user to enable several features to produce data. The following table summarizes the dependencies:
| Feature | Dependencies (Realtime) | Dependencies (Historical) |
| Sources | None, always supported | Traffic logging enabled in policy |
| Destinations | None, always supported | Traffic logging enabled in policy |
| Interfaces | None, always supported | Disk logging enabled
Traffic logging enabled in policy |
| Policies | None, always supported | Disk logging enabled
Traffic logging enabled in policy |
| All Sessions | None, always supported | Traffic logging enabled in policy |
| Applications | None, always supported | Disk logging enabled
Traffic logging enabled in policy Application control enabled in policy |
Configuration Dependencies
| Feature | Dependencies (Realtime) | Dependencies (Historical) |
| WiFi Clients | SSID must be in Tunnel mode | Disk logging enabled
Traffic logging enabled in policy SSID must be in Tunnel mode |
| Cloud Applications | Not supported | Disk logging enabled
Application control enabled in policy SSL “deep inspection” enabled in policy Deep application inspection enabled in application sensor Extended UTM log enabled in application sensor |
| Web Sites | Disk logging enabled
Web Filter enabled in policy “web-url-log” option enabled in Web Filter profile |
Disk logging enabled
Web Filter enabled in policy “web-url-log” option enabled in Web Filter profile |
| Threats | Not supported | Disk logging enabled
Traffic logging enabled in policy Threat weight detection enabled |
| Threat Map | None, always supported | Disk logging enabled
Traffic logging enabled in policy Threat weight detection enabled |
| FortiSandbox | Not supported | Disk logging enabled
Traffic logging enabled in policy |
| System Events | Not supported | Disk logging enabled |
| VPN | Not supported | Disk logging enabled
Traffic logging enabled in policy |
Having trouble configuring your Fortinet hardware or have some questions you need answered? Check Out The Fortinet Guru Youtube Channel! Want someone else to deal with it for you? Get some consulting from Fortinet GURU!
Hello Mike,
Useful and interesting Post !
I have some trouble with fortiview and i’d love to ask a questions,
I have two FortiGate devices in two different companies, FG VM64 and FG-200E.
Under fortiview / Traffic from LANDMZ / Sources, i want to see and filter logs by “user”.
FG-200E can filter by username and also has many other options to filter logs, but FGVM64 has only “Source” and “Source Device” filter applicable.
My question is: Doesn’t VM64 supports other filter options or do i have to turn something on to enable filter options ?
Note: FG200E is logging in memory, whether FGVM64 has Disk logging enabled. Both of them has traffic logging enabled (Under policy / Logging option / Log Allowed Traffic / All Sessions) and both of them are using DC Agent to poll user database from AD. I know DC Agent is configured well because everything else is working fine and i can see users under Monitor / Firewall user monitor and under Log&Report / Forward traffic.
I already tried using different Browsers.
Regards.
So both FortiGates are configured the same? The only difference is the platform it is on? (appliance vs VM)
Hello and thanks for a quick response !
No, configurations are different, but both are using DC agent to poll users from AD and then users are matched under different policies to give them different web access privileges.
Under fortiview/source, Physical version has way more options to filter traffic, than VM version.
But Yesterday i asked friend of mine, who has FG100E (no DC agent on it, used as transparent) and he also has no that additional filters available. So i dont think that its Physical/Virtual related.
Could it be because of software version ?
FG200E: v6.0.2
FG100E and VM: v6.0.4
Hello Mike,
I configured fortigate to serve as web proxy, i configured the rules under proxy tab, no rules in the IPv4 policy section. I am not seeing logs in fortiview, but when i go to the proxy policy and i right-click and click on ‘show matching logs’, i can see see logs.
What am i doing wrongly
What version of code are you running?