sorted by: recent | see : popular

Content Tagged with syslog + linux

Below is documentation for using SourceLabs Self-Support Suite for Linux and Open Source Java to gather, organize, and search Syslog messages.

You can setup syslog to connect to the relay. In this release, we only support syslog over UDP. To set this up, you need to modify your syslogd config file. Often this is in /etc/syslog.conf

To get started, you can add

. @relayMachineName:4657

This will send all your syslog messages to a machine named relayMachineName over port 4657. Port 4657 is the default port the relay listens to for Syslog UDP messages. You can change this in the relay’s property file. This properties file is located in the ‘conf’ directory of your relay installation (e.g. /opt/sourcelabs/relay/conf).

To filter the syslog messages sent to the relay, please read the syslog documentation or man pages for more information.

Syslog-ng:

You can also setup syslog-ng to use the relay. For the current version of the relay, you will need to use UDP logging to the relay instead of TCP. To set this up, you need to modify your syslog-ng config file. Often this is in /etc/syslog-ng.conf

Assuming that you are using a default syslog-ng configuration where source ‘s_sys’ represents all syslog messages (modify source as necessary for your configuration),this will send all your syslog messages to a machine named relayMachineName over port 4657. Port 4657 is the default port the relay listens to for Syslog UDP messages. You can change this in the relay’s property file. This properties file is located in the ‘conf’ directory of your relay installation (e.g. /opt/sourcelabs/relay/conf).

To filter the syslog messages sent to the relay, please read the syslog documentation or man pages for more information.

Find more information about SourceLabs Self-Support Suite for LInux and Open Source Java