Path: Configuration > Logs > Syslog > Settings
Message Generation: Enable the generation and the logging of Syslog messages for events that have Syslog
configured as a notification method.
Facility Code: Selects the facility code assigned to the Syslog messages of the ATS (User, by default).
NOTE: User best defines the Syslog messages sent by the ATS. Do not change this selection unless advised
to do so by the Syslog network or system administrator.
Severity Mapping: This section maps each severity level of the ATS or environment events to available
Syslog priorities. The local options are Critical, Warning, and Informational. You should not need to change
the mappings.
• Emergency: The system is unusable
• Alert: Action must be taken immediately
• Critical: Critical conditions
• Error: Error conditions
• Warning: Warning conditions
• Notice: Normal but significant conditions
• Info: Informational messages
• Debug: Debug-level messages
The following are the default settings for Local Priority:
• Critical is mapped to Critical
• Warning is mapped to Warning
• Informational is mapped to Info
Test Syslog servers
Path: Configuration > Logs > Syslog > Test
Send a test message to the Syslog servers (configured through the “Syslog servers” page). The result will be
sent to all configured Syslog servers.
Select a severity to assign to the test message and then define the test message. Format the message to
consist of the event type (for example, APC, System, or Device) followed by a colon, a space, and the event
text. The message can have a maximum of 50 characters.
• The priority (PRI): the Syslog priority assigned to the message event, and the facility code of
messages sent by the ATS.
• The Header: a time stamp and the IP address of the ATS.
• The message (MSG) part.
• The TAG field, followed by a colon and space, identifies the event type.
• The CONTENT field is the event text, followed (optionally) by a space and the event code.
Example: APC: Test Syslog is valid.
