Chat now with support
Tchattez avec un ingénieur du support

syslog-ng Premium Edition 7.0.18 - Release Notes

Release Notes

syslog-ng Premium Edition 7.0.18

Release Notes

January 2020

These release notes provide information about the syslog-ng Premium Edition release.

About this release

Welcome to syslog-ng Premium Edition (syslog-ng PE) version 7 and thank you for choosing our product. This document describes the new features and most important changes since the latest release of syslog-ng PE. The main aim of this paper is to aid system administrators in planning the migration to the new version of syslog-ng PE. The following sections describe the news and highlights of syslog-ng PE 7.

Starting with version 7, syslog-ng Premium Edition is released as a rolling release. For details, see the Version policy.

Supported platforms

The syslog-ng Premium Edition application is officially supported on the following platforms. Note that the following table is for general reference only, and is not always accurate about the supported platforms and options available for specific platforms. The latest version of this table is available at https://syslog-ng.com/log-management-software/supported-platforms. Unless explicitly noted otherwise, the subsequent releases of the platform (for example, Red Hat Enterprise Linux 7 and its update releases like 7.2) are also supported.

Table 1: Platforms supported by syslog-ng Premium Edition

x86 x86_64 SPARC SPARC64 PowerPC IA64
CentOS 6 - - - - -
CentOS 7 - - - - -
Debian 8 (jessie) - - - - -
Oracle Linux 6 - - - - -
Oracle Linux 7 - - - - -
Red Hat EL 6 - - - - -
Red Hat EL 7 - - - - -
SLES 12 - - - - -
Ubuntu 16.04 LTS (Xenial Xerus) - - - - -
Ubuntu 18.04 LTS (Bionic Beaver) - - - - -

Caution:

Certain sources and destinations are not supported on every platform (particularly, the sql() destination, and the hdfs() destination). For details, see the description of the specific source and destination.

Caution:

If you are planning to use Python in syslog-ng PE (for example, Python parser or Python template function) on RHEL 6 platform, then you have to manually install Python 2.7. If the Python version on the machine is not 2.7, you will receive a similar error message during startup:

[2017-07-27T13:42:03.606679] Reading shared object for a candidate module: path='/opt/syslog-ng/lib/syslog-ng', fname='mod-python.so', module='mod-python' [2017-07-27T13:42:03.606994] Error opening plugin module: module='mod-python', error='libpython2.7.so.1.0: cannot open shared object file: No such file or directory'

For details about the syslog-ng Agent for Windows application, see the syslog-ng Agent for Windows documentation. For an agent-less solution, see the list of supported platforms.

For using syslog-ng PE on other platforms (for example, AIX, FreeBSD, HP-UX, Solaris, Microsoft Windows), see the list of supported platforms in the syslog-ng PE version 6 Administration Guide.

New features in syslog-ng PE 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
Outils libre-service
Base de connaissances
Notifications et alertes
Support produits
Téléchargements de logiciels
Documentation technique
Forums utilisateurs
Didacticiels vidéo
RSS Feed
Nous contacter
Obtenir une assistance en matière de licence
Support Technique
Afficher tout
Documents connexes