syslog() Source/Destination Driver
The syslog() driver can be used to send and receive messages from the network using the standard IETF-syslog protocol.
Important Information
Please keep in mind, that the syslog() driver using the standard IEFT-syslog protocol for sending and receiving messages. The IEFT protocol uses frames to separate the individual messages instead of a newline character, thus prototyping with tools such as Netcat might result in an invalid header error.
NOTE: The syslog() driver can also receive/send the legacy BSD-syslog-formatted messages. The syslog driver also includes TCP messaging on a TLS-encrypted channel, however, this is tested and verified in a separate post dealing with TLS-encryption with syslog-ng here.
Status
Protocol
Architecture
Source
Destination
UDP
x86
Works
Works
UDP
ARM
Works
Works
TCP
x86
Works
Works
TCP
ARM
Works
Works
How to test
Configuration Files Used
To test the syslog driver -- both source and destination drivers, we will run two instances of syslog-ng. One where we are transmitting data using the syslog destination driver that needs to be tested. And another that will listen for the data on the network pipeline established using the syslog source driver.
Destination Configuration File
(Note: For more information on how to do conditional destination routing and using template function, click here.)
Source Configuration File
Proof
Last updated