The new docs.trellix.com offers a modernized UI and AI-powered features like conversational searches. Content is currently available only in English. Other languages will be available in mid-October 2026. We hope you enjoy the new experience.

Syslog relay support

Prev Next

Forwarding events from various devices through a syslog relay server to the Receiver requires additional steps.

You must add a single syslog relay data source to accept the stream of data and additional data sources. This allows the Receiver to split up the stream of data into the originating data sources. Sylog-ng and Splunk are supported. This diagram describes this scenario:

GUID-08C759D0-B255-45FB-8896-6D0C90E815A7-low.png

  1. Cisco ASA Device

  2. SourceFire Snort Device

  3. TippingPoint Device

  4. Syslog Relay

  5. Data Source 1 — Syslog Relay

  6. Data Source 2 — Cisco ASA

  7. Data Source 3 — SourceFire Snort

  8. Data Source 4 — TippingPoint

Using this scenario as an example, you must set up the syslog relay data source (5) to receive the stream of data from the syslog relay (4), selecting syslog in the Syslog relay field. Once the syslog relay data source is set up, add the data sources for the individual devices (6, 7, and 8), selecting None in the Syslog relay field, because this device is not a syslog relay server.

Note

Upload Syslog Messages does not work on a syslog relay setup.

The header on the syslog must be configured to look like the following example: 1 <123> 345 Oct 7 12:12:12 2012 Host_Name.com httpd[123]

where

 

1 =

syslog version (optional)

 

345 =

syslog length (optional)

 

<123> =

facility (optional)

 

Oct 7 12:12:12 2012 =

date; hundreds of formats are supported (required)

 

Host_Name.com

hostname or ip address (ipv4 or ipv6) (required)

 

httpd =

application name (optional)

 

[123]

application pid (optional)

 

: =

a colon (optional)

Note

The host name and data fields can appear in either order. An IPv6 address can be enclosed in brackets [ ].