Syslog Configuration

Overview

Synaccess SP and DX devices can send selected activity and event logs to a remote syslog
server. This allows device logs to be collected by a central logging platform
for monitoring, auditing, and troubleshooting.

Available settings may vary by device model and firmware version.

When to Use Syslog

Remote syslog is useful when you want to:

• Collect logs from multiple devices in one location
• Keep a centralized activity history
• Monitor configured device events
• Support troubleshooting and incident review
• Send device logs to a compatible log management or SIEM platform

Configure Remote Syslog

1. Sign in to the device web interface.
2. Open Logging > Syslog.
3. Enter the remote syslog server address and port.
4. Select UDP or TCP.
5. If TCP is selected, enable encrypted logging when required by the receiving
   server.
6. Enable one or both of the following:
   • Log User Activity Remotely
   • Log Events Remotely
7. Select Save.

Example server address:

Text

192.168.1.201:514

The specified server must be reachable from the device. Any intervening
firewall must allow traffic on the configured protocol and port.

Available Log Types

User Activity

User Activity logs record supported actions performed by users, such as
configuration changes and device control operations.

The Enable Logging of Outlet Switching/Power Cycling setting controls
whether supported manual outlet switching and power-cycling actions are
included in the activity log.

Events

Event logs record device events configured under the device's automation
settings. The exact messages depend on the events and actions configured on the
device.

Log Format

Logs use a traditional syslog-style text format. A message generally contains:

• Timestamp
• Device hostname
• Message category
• Human-readable message

General structure:

Text

<timestamp> <hostname> <category>: <message>

Illustrative example:

Text

Jul 28 14:32:10 PDU-01 USER_ACTIVITY: Outlet 1 switched on by admin

The precise category and message text vary by action, event, device model, and
firmware version. Integrations should avoid depending on the exact wording of a
message unless the format has been confirmed for the firmware release in use.

Protocol Options

UDP

UDP has low transmission overhead but does not confirm delivery. Use it when
the receiving server expects standard UDP syslog and occasional packet loss is
acceptable.

TCP

TCP provides a persistent, reliable transport connection. Use it when delivery
reliability is more important or when required by the receiving server.

Encrypted TCP

Encrypted logging is available when TCP is selected. The receiving syslog
server must be configured for a compatible encrypted TCP connection on the
specified port.

Expected Behavior

• Local logging continues when remote logging is enabled.
• Only the selected User Activity and Event log types are sent remotely.
• Log timestamps use the time configured on the device.
• Changing the remote syslog settings applies the new configuration after it
  is saved.

Troubleshooting

If logs do not appear on the remote server:

1. Confirm that the server address and port are correct.
2. Confirm that the selected protocol matches the server configuration.
3. Verify that the appropriate remote log type is enabled.
4. Check routing and firewall rules between the device and server.
5. If encrypted TCP is enabled, confirm that the receiver is listening for an
   encrypted connection on the configured port.
6. Confirm that the device date, time, and time zone are correct.
7. Generate a supported user action or configured event and check the server
   again.

Limitations and Compatibility

• Available settings and message text may differ between firmware releases.
• UDP does not guarantee message delivery.
• The remote server must support the selected protocol and connection type.
• For integrations that require exact field mappings or parsing rules, confirm
  the device model, firmware version, and receiving platform with Synaccess
  Support.