Syslog Listener
Most recent version: v1.1.2
Learn more about this Listener type in this article.
v1.1.2
Released on 08/27/2025
Solved panic throwing with malformed Syslog messages. Improperly formatted Syslog messages previously caused the application to crash, whereas now it will properly validate and safely processe malformed Syslog data.
v1.0.2
Released on 04/09/2025
The
sourceIpandsourcePortfields are unmarshaled correctly now. This fix resolves an issue where the system previously failed to properly extract or convert the sourceIp and sourcePort fields during data parsing (unmarshaling). Now, these network identifier fields are correctly interpreted from their serialized format into their proper data types and structures, ensuring accurate representation of connection origins.IP is now sent as a string to speed up marshaling/unmarshaling.
v1.0.1
Released on 03/10/2025
RFC5424 events with missing messages are unmarshaled correctly now. This fix addresses a parsing issue with RFC5424-formatted syslog events that lack message content. With this update, the unmarshaling process now correctly handles these edge cases, ensuring that valid syslog events are properly processed even when they contain only metadata without an actual message payload.
v0.1.1
Released on 07/23/2024
Prioritized NTF when auto-detecting framing method. Onum now prioritizes Network Transmission Format (NTF) when identifying message framing methods in data streams. The hexadecimal delimiter
0C(form feed character) will only be recognized as a frame boundary when it's immediately followed by whitespace.Added support for RFC3164 tag options, considering them part of the tag itself.
The proceed reported between square brackets and immediately following the tag under RFC3164 is no longer mandatory.
Last updated
Was this helpful?