Logging must be enabled for each individual log type before log messages will recorded to disk. See config log attack-log, config log event-log, and config log traffic-log for details. |
Variable | Description | Default |
status {enable | disable} | Enable to store log messages on the local hard disk. Log messages are stored only if logging is enabled for the individual log types using the config log attack-log, config log event-log, and config log traffic-log commands. Also configure severity, diskfull and max‑log‑file‑size. | enable |
diskfull {nolog | overwrite} | Type what the FortiWeb appliance will do when the local disk is full and a new log message is caused, either: • nolog — Discard the new log message. • overwrite — Delete the oldest log file in order to free disk space, then store the new log message. This field is available only if status is enable. | overwrite |
max-log-file-size <file-size_int> | Type the maximum size in megabytes (MB) of the current log file. When the log file reaches the maximum size the log file is rolled (that is, the current log file is saved to a file with a new name, and a new log file is started). The valid range is between 100 and 200 MB. This field is available only if status is enable. | 100 |
severity {alert | critical | debug | emergency | error | information | notification | warning} | Select the severity level that a log message must meet or exceed in order to cause the FortiWeb appliance to record it. | information |