syslog-ng Premium Edition 7.0.14 - Release Notes

Highlights of 7.0

Enriching data

You can use an external database file to append custom name-value pairs to incoming logs, thus extending, enriching, and complementing the data found in the log message. For example, you can create a database (or export it from an existing tool) that contains a list of hostnames or IP addresses, and the department of your organization that the host belongs to, the role of the host (mailserver, webserver, and so on), or similar contextual information. For details, see "Enriching log messages with external data" in the Administration Guide.

You can correlate and aggregate information from log messages using a few simple filters that are similar to SQL GROUPBY statements. You do not even have to configure a pattern database. Also, when correlating messages containing numerical information, you can use numerical template functions that work on numerical values of a correlation context. For details, see "Correlating log messages" in the Administration Guide and "Template functions of syslog-ng PE" in the Administration Guide.

Improved configuration flexibility

You can define configuration objects inline, where they are actually used, without having to define them in a separate object. This is useful if you need an object only once, for example, a filter or a rewrite rule, because it makes the configuration much easier to read. Every object can be defined inline: sources, destinations, filters, parsers, rewrite rules, and so on. For details, see "Defining configuration objects inline" in the Administration Guide.

From now on, every configuration object is a log expression. Every configuration object is essentially a configuration block, and can include multiple objects. To reference the block, only the top-level object must be referenced. That way you can use embedded log statements, junctions and in-line object definitions within source, destination, filter, rewrite and parser definitions. For example, a source can include a rewrite rule to modify the messages received by the source, and that combination can be used as a simple source in a log statement. This feature allows you to preprocess the log messages very close to the source itself. For details, see "Using channels in configuration objects" in the Administration Guide.

To make the configuration more readable, and to help avoid misconfiguration, you can use human-readable units when setting configuration options, for example, log-fifo-size(2Mb). For details, see "Notes about the configuration syntax" in the Administration Guide.

Other changes
  • The default value of log-msg-size() is 8192 instead of 65536. Increase it if needed.

  • The skip-cluster-health-check() option is available for the elasticsearch2() destination. For details, see "Elasticsearch2 destination options (DEPRECATED)" in the Administration Guide.

  • The qdisk-dir option of syslog-ng PE is not available as a command-line option, use the dir() option of disk-buffer() in the configuration of the destination instead.

  • Several features and platforms that are available in syslog-ng Premium Edition 6 LTS are not yet available in syslog-ng PE 7. For details, see Features available only in syslog-ng PE 6 LTS.

Deprecated features

The following is a list of features that are no longer supported starting with syslog-ng PE 7.0.14.

  • Version 7.0.14 and later does not support the Debian Wheezy and Ubuntu 12.04 LTS (Precise Pangolin) platforms.

  • Since ElasticSearch version 1.x has reached its end of life, its support has been removed from syslog-ng PE. Use the elasticsearch2 destination instead.

Resolved Issues

The following is a list of issues addressed in this release.

Table 2: General resolved issues in syslog-ng PE 7.0.14
Resolved Issue Issue ID

Crash in network source with ALTP due to idle timer

SYSLOGDEV-4711

OpenSSL 1.0.2r upgrade

SYSLOGDEV-4742

http-destination stuck when reverting to old configuration

SYSLOGDEV-4747

syslog-ng segmentation fault on statistics query

SYSLOGDEV-4759

WEC: Adds list support to Windowsevent-parser

SYSLOGDEV-4789

Table 3: General resolved issues in syslog-ng PE 7.0.13
Resolved Issue Issue ID

Fix loggen parameters

SYSLOGDEV-4684

Fix seeking in logstore using lgstool cat command

SYSLOGDEV-4680

Empty disk queue truncate fix

SYSLOGDEV-4628

Memory leak during reload when using the app-parser

SYSLOGDEV-4564

Race condition during reload when using license-counter-reset

SYSLOGDEV-4540

Table 4: General resolved issues in syslog-ng PE 7.0.12
Resolved Issue Issue ID

non-reliable diskq: fixes false positive corruption detection

SYSLOGDEV-4674

Dqtool reported disk queue corrupted false positively

SYSLOGDEV-4407

Append $(basename) to filename template correctly

SYSLOGDEV-4673

SSL: Multiple ca-dir() related issues fixed

SYSLOGDEV-4669

Fix frequent disconnects of syslog() driver when using TLS

SYSLOGDEV-4667

OpenSSL upgraded to 1.0.2q

SYSLOGDEV-4650

File destination fd leak after reload when time-reap elapsed

SYSLOGDEV-4609

hdfs: fd leak during reload

SYSLOGDEV-4581

tls: Handle allow-compress correctly

SYSLOGDEV-4580

Socket leak when using udp destination with spoof-source enabled

SYSLOGDEV-4552

Features available only in 6 LTS

Features available only in syslog-ng PE 6 LTS

In general, syslog-ng Premium Edition version 7 has much more features than version 6 LTS, therefore One Identity recommends using version 7 for all deployments, except when a feature that you require is only available in version 6 LTS. In case you need help with migrating from version 6 LTS to 7, contact our Support Team for help. Also note that as an alternative to the syslog-ng Agent for Windows application, syslog-ng PE version 7 supports an agent-less solution to fetch log messages from Windows hosts.

The following features that are available in syslog-ng Premium Edition 6 LTS are not yet available in syslog-ng PE 7.

  • The SNMP destination (snmp()).

  • The SQL source (sql()).

  • The allow-compress(), ca-dir-layout(), and cert-subject() options related to TLS transport.

  • The syslog-ng PE 7 application is currently supported only on Linux platforms. For a detailed list, see "Supported platforms" in the Administration Guide.

  • The spoof-interface() options of the network() and syslog() destinations.

  • The read-old-records() and use-syslogng-pid() options of the file() source.

  • The replace(), cut(), and format-snare() template-functions.

  • FIPS-compliant packages are not available.

Platforms not supported in syslog-ng PE 7
  • AIX

  • FreeBSD

  • HP-UX

  • Oracle Linux 5, 6

  • openSUSE

  • Solaris

  • Windows

For a complete list of supported platforms, see "Supported platforms" in the Administration Guide.

Related Documents