The local log is a datastore hosted on the FortiADC system.
Typically, you use the local log to capture information about system health and system administration activities. We recommend that you use local logging during evaluation and verification of your initial deployment, and then configure remote logging to send logs to a log management repository where they can be stored long term and analyzed using preferred analytic tools.
Local log disk settings are configurable. You can select a subset of system events, traffic, and security logs.
Before you begin:
- You must have Read-Write permission for Log & Report settings.
To configure local log settings:
- Go to Log & Report > Log Setting.
- Complete the configuration as described in Local logging configuration.
- Save the configuration.
The configuration page displays the Local Log tab.
|Status||Select to enable local logging.|
|File Size||Maximum disk space for a local log file. The default is 200 MB. When the current log file reaches this size, a new file is created.|
|Log Level||Select the lowest severity to log from the following choices:
For example, if you select Error, the system collects logs with level Error, Critical, Alert, and Emergency. If you select Alert, the system collects logs with level Alert and Emergency.
|Disk Full||Select log behavior when the maximum disk space for local logs (30% of total disk space) is reached:
|Event||Select to enable logging for events.|
This option becomes available only when the Event check box is selected. In that case, select the types of events to collect in the local log:
Select to enable logging for traffic processed by the load balancing modules.
The following options become available only when the Traffic check-box is selected. See above.
Select to enable logging for traffic processed by the security modules.
Select to enable scripting.
|Script Category||SLB is selected by default and required.|