v2.5.3

Delimit syslog entries by valid priority header

This release relaxes the syslog entry delimiter to a valid priority header. In the previous release, v2.5.2, additional characters beyond the priority header were used. In practice, these characters are highly variable and do not adhere to RFC 3164 standards, which leads to the loss of non-canonical RFC 3164 data. Therefore, this release supports accepting a wider variety of RFC 3164 logs at the cost of a less stringent delimiter.

v2.5.2

Support < character in log body

This release allows syslog entries to contain < outside of the priority header. It enables the standardization of the < delimiter introduced in v2.5.0.

v2.5.1

Restrict traffic to that which starts with <

This release restricts traffic parsed by go-syslog to that which starts with <. It logically completes standardization of the < delimiter introduced in v2.5.0.

v2.5.0

Support multiple message batching formats

This release is aimed at making go-syslog more robust by supporting multiple message batching formats. It standardizes the < character delimiter since it is the first character of every syslog message. In addition, it introduces log statements for troubleshooting network connections.

v2.4.0

Support standard TLS by default

This release is aimed at making go-syslog more robust by supporting standard TLS connections out-of-the-box