Use this command to configure the FortiWeb appliance to send log messages to a Syslog server defined by log syslog-policy .
|For improved performance, unless necessary, avoid logging highly frequent log types. While logs sent to your Syslog server do not persist in FortiWeb’s local RAM, FortiWeb still must use bandwidth and processing resources while sending the log message.
To use this command, your administrator account’s access control profile must have either
rw permission to the
loggrp area. For details, see Permissions.
config log syslogd
Enable to send log messages to the Syslog server defined by log syslog-policy. Also configure:
Enter the facility identifier that the FortiWeb appliance will use to identify itself when sending log messages to the first Syslog server.
To easily identify log messages from the FortiWeb appliance when they are stored on the Syslog server, enter a unique facility identifier, and verify that no other network devices use the same facility identifier.
|Select the severity level that a log message must meet or exceed in order to cause the FortiWeb appliance to send it to the first Syslog server.
If logging to a Syslog server is enabled, enter the name of a Syslog policy which describes the Syslog server to which the log message will be sent. The maximum length is 63 characters.
For details about on Syslog policies, see log syslog-policy.
This example enables storage of log messages with the
notification severity level and higher on the Syslog server. The network connections to the Syslog server are defined in
Syslog_Policy1. The FortiWeb appliance uses the facility identifier
local7 when sending log messages to the Syslog server to differentiate its own log messages from those of other network devices using the same Syslog server.
config log syslogd
set status enable
set severity notification
set facility local7
set policy "Syslog_Policy1"