Chat now with support
Chat with Support

syslog-ng Premium Edition 7.0.20 - Release Notes

New features in syslog-ng PE version 7.0.19

The syslog-ng PE application uses its own Python interpreter

Starting from version 7.0.20, the syslog-ng PE application uses its own Python interpreter (shipped with the default syslog-ng PE installation) instead of the system's Python interpreter.

New features in syslog-ng PE version 7.0.18

Receiving large volume of UDP messages

Starting with syslog-ng PE version 7.0.18, you receive UDP logs at very high-volume using the new udp-balancer() source. The udp-balancer() source allows you to use multiple CPU cores to process the incoming UDP messages at a very high message rate, depending on the available hardware resources, incoming message size, and your syslog-ng PE configuration. Note that this feature requires a recent Linux kernel, so it is supported only selected platforms. For details, see "udp-balancer: Receiving UDP messages at very high rate" in the Administration Guide.

Enhancements

The default-network-drivers() source now supports the max-connections() option.

NOTE:

Starting with 7.0.19, syslog-ng PE assigns a persist name to Python sources and destinations. The persist name is generated from the class name. If you want to use the same Python class multiple times in your syslog-ng PE configuration, add a unique persist-name() to each source or destination, otherwise syslog-ng PE will not start. For example:

log {
    source { python(class(PyNetworkSource) options("port" "8080") persist-name("<unique-string>); };
    source { python(class(PyNetworkSource) options("port" "8081")); };
  };

Alternatively, you can include the following line in the Python package: @staticmethod generate_persist_name. For example:

from syslogng import LogSource
  class PyNetworSource(LogSource):
    @staticmethod
    def generate_persist_name(options):
        return options["port"]
    def run(self):
        pass
    def request_exit(self):
        pass

New features in syslog-ng PE 7.0.17

Fetching logs from Office 365

Starting with syslog-ng PE version 7.0.17, you can fetch logs from your Office 365 account using the Office 365 Management Activity API. For details, see "office365: Fetching logs from Office 365" in the Administration Guide.

Upgrade improvements

The upgrade from syslog-ng PE version 6 has been improved and made more robust. If you are upgrading from syslog-ng PE version 6, first upgrade to the latest available 6.0.x maintenance release. For details on the upgrade process to syslog-ng PE version 7, see "Upgrading from None 6.0.x to version None" in the Administration Guide.

New features in syslog-ng PE 7.0.16

Enhancements

Detailed documentation about upgrading from syslog-ng PE 6 to version 7 is available at "Upgrading from None 6.0.x to version None" in the Administration Guide.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating