Configuring the Remote Syslog Server
The controller maintains an internal log file of current events and alarms, but this internal log file has a fixed capacity. Configure the log settings so you can keep copies of the logs that the controller generates.
At a certain point, the controller will start deleting the oldest entries in log file to make room for newer entries. If you want to keep a permanent record of all alarms and events that the controller generated, you can configure the controller to send the log contents to a syslog server on the network.
Follow these steps to configure the remote syslog server:
- Go to System > General Settings > Syslog.
- Select the Enable logging to remote syslog server check box.
- Configure the settings as explained in the table below.
- Click OK.
Field | Description | Your Action |
---|---|---|
Primary Syslog Server Address | Indicates the syslog server on the network. |
|
Secondary Syslog Server Address | Indicates the backup syslog server on the network, if any, in case the primary syslog server is unavailable. |
|
Application Logs Facility | Indicates the facility for application logs. |
|
Administrator Activity Logs Facility | Indicates the facility for administrator logs. |
|
Other Logs Filter Severity | Indicates the facility for comprehensive logs. | Select one of the following Filter Severity:
|
Event Facility | Indicates the facility for event logs. | Select the option from the drop-down. Range: 0 through 7. |
Event Filter | Indicates the type of event that must be sent to the syslog server. | Choose the required option:
|
Event Filter Severity applies to Event Filter > All events above a severity | Indicates the lowest severity level. Events above this severity level will be sent to the syslog server. | Select the option from the drop-down:
|
Priority | Indicates the event severity to syslog priority mapping in the controller. | Choose the Syslog Priority among
Error,
Warning,
Info and
Debug, for the following event severities:
|