Syslog
Most recent version: v1.0.2
Last updated
Was this helpful?
Most recent version: v1.0.2
Last updated
Was this helpful?
Onum receives data from Syslog, supporting TCP and UDP protocols.
Select Syslog from the list of Listener types and click Configuration to start.
Now you need to specify how and where to collect the data, and how to establish a connection with Syslog.
Enter the basic information for the new Listener.
Name*
Enter a name for the new Listener.
Description
Optionally, enter a description for the Listener.
Tags
Add tags to easily identify your Listener. Hit the Enter key after you define each tag.
Note that you won't see the Port and Protocol settings in the creation form if you're defining this Listener in a Cloud instance, as these are already provided by Onum.
Port*
Enter the IP port number. While UDP 514 is the standard, some implementations may use TCP 514 or other ports, depending on specific configurations or security requirements. To determine the syslog port value, check the configuration settings of your syslog server or consult the documentation for your specific device or application.
Protocol*
Onum supports TCP and UDP protocols.
Framing Method*
The Framing Method refers to how characters are handled in log messages sent via the Syslog protocol. Choose between:
Auto-Detect - automatically detect the framing method using the information provided.
Non-Transparent Framing (newline) - the newline characters (\n) within a log message are preserved as part of the message content and are not treated as delimiters or boundaries between separate messages.
Non-Transparent Framing (zero) - refers to the way zero-byte characters are handled. Any null byte (\0) characters that appear within the message body are preserved as part of the message and are not treated as delimiters or boundaries between separate messages.
Octet Counting (message length) - the Syslog message is preceded by a count of the length of the message in octets (bytes).
Note that the parameters in this section are only mandatory if you decide to include TLS authentication in this Listener. Otherwise, leave it blank.
Certificate*
This is the predefined TLS certificate.
Private key for this listener*
The private key of the corresponding certificate.
CA chain
The path containing the CA certificates.
Client authentication method*
Choose between No, Request, Require, Verify, and Require & Verify.
Minimum TLS version*
Select the required version from the menu.
Note that you won't see this section in the creation form if you're defining this Listener in a Cloud instance, as these are already provided by Onum. Learn more about Cloud Listeners in .
Click Create labels to move on to the next step and define the required if needed.
