Insider 2018-10: 3.18 release; Splunk .conf18; Python destination; Python parser;

Dear syslog-ng users,

This is the 70th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news.



Version 3.18 of syslog-ng released

Version 3.18 of syslog-ng has been released with plenty of new features and bugfixes. Performance of the HTTP destination improved thanks to batching and multi-threading. The new Python source allows you to create source drivers for syslog-ng in Python.

Learn about the small, but important changes at or read the complete list of changes at

syslog-ng at Splunk .conf18

Balázs Scheidler, original author of syslog-ng, gave a talk at the annual Splunk conference. His talk about simplifying complex log data ingestion with syslog-ng is now available on-line. Learn about the new features coming up in syslog-ng to make it an even better choice to feed Splunk with log data:

Python destination

You can send your log messages to many different destinations using syslog-ng, but of course not everywhere. This is where the Python destination of syslog-ng can come handy. You can extend syslog-ng easily with your own code written in Python and store your log messages to the destination of your choice.

Learn how to develop your own Python code for syslog-ng from our blog series, starting with the very basics and showing a complete working MQTT destination implemented in Python at the end:

Python parser

The Python parser of syslog-ng not only enables you to parse any type of log message, but you can also use it to enrich messages. From this blog you will learn how to extract information from a specially formatted log message, and how to create new name-value pairs by consulting external databases about data contained in your log messages. I will show these using two simple parsers: one resolves host names from IP addresses, the other one uses regular expressions to parse synthetic log messages from the loggen utility.


You can watch our past webinars:

Your feedback and news, or tips about the next issue are welcome.