Released: Fri, 03 May 2019
#SYSLOGDEV-4742 - OpenSSL 1.0.2r upgrade -- OpenSSL upgraded to version 1.0.2r
#SYSLOGDEV-4747 - http-destination stuck when revert to old config -- syslog-ng reload stuck using http destination
#SYSLOGDEV-4789 - WEC: Windowsevent-parser list support -- WEC: Handle XML list type data
#SYSLOGDEV-4711 - Crash in network source with ALTP due to idle timer -- Crash using ALTP source
#SYSLOGDEV-4759 - syslog-ng segmentation fault on statistics query -- Crash caused by syslog-ng-ctl stats query
Google Stackdriver destination
The stackdriver destination of syslog-ng PE can send log messages to the Google Stackdriver cloud. Google Stackdriver is a widely used metrics, event, and log aggregator and analyzer system.
Elasticsearch HTTP destination
Version 7.0.14 of syslog-ng PE can directly post log messages to an Elasticsearch deployment using the Elasticsearch Bulk API over the HTTP and Secure HTTP (HTTPS) protocols.
Windows Server 2019 logs
The Windows Event Collector application now supports Windows Server 2019.
The syslog-ng-ctl reload command now has a return value: 0 if the operation was successful, 1 otherwise.
Instead of dropping incoming messages that are too long, you can now trim them using the trim-large-messages() option of the syslog() source.
Platform support changes:
Debian 7 (wheezy) platform is unsupported from 7.0.14 version.
Manual configuration upgrade needed
Since there are some missing features/options it is possible you will need to change parts of your configuration file. In case you need help with upgrading please contact the One Identity Support Team for advice.
Platforms supported in syslog-ng PE 7
Debian 8 (jessie)
Oracle Linux 7
Oracle Linux 6
Red Hat EL 7
Red Hat EL 6
Ubuntu 12.04 LTS (Precise Pangolin)
Ubuntu 14.04 LTS (Trusty Tahr)
Ubuntu 16.04 LTS (Xenial Xerus)
Ubuntu 18.04 LTS (Bionic Beaver)
Platforms not supported in syslog-ng PE 7
Oracle Linux 5