Insider 2016-06: Red Hat; 3.8 RPMs; BMW; MongoDB; FLARE; Java;

Dear syslog-ng users,

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


Meet syslog-ng at Red Hat Summit

This year Balabit is sponsoring the Red Hat Summit again. The event
will be held in Moscone Center North in San Francisco, June 27-29.
Visit Balabit’s booth (booth #918) and meet Balázs Scheidler, the
author of syslog-ng. You can request an appointment at

If you want to meet him outside of the conference floor, there will
also be a meetup in Café Prague on the 30th of June:

Preview syslog-ng 3.8 RPM packages and send us your feedback

While syslog-ng 3.8 does not yet have an alpha release, it already has
many interesting features. As it is still under heavy development, we
can’t recommend it for production use. On the other hand, any feedback
is very welcome. New features include disk buffer, Elasticsearch 2
support, grouping-by, Rust-based parsers, and so on:

syslog-ng in the BMW i3

While most people know syslog-ng as a central syslog server, there is
another use, which is less known but most likely has a lot larger
installed base. It is syslog-ng embedded. Read how BMW is utilizing
syslog-ng at
and let us know how you use syslog-ng!

MongoDB changes in 3.8

Under the hood, the driver to access MongoDB databases was replaced in
syslog-ng 3.8. Read about the advantages of the new driver and how it
affects configuration at:

FLARE: Filtered Log Alert and Reporting Engine

FLARE staplies together syslog-ng, ELK, Alerting and Incident Response
with metadata. The aim was to develop a solution that is able to
provide a unified view of log events and incidents, helping the work
of operations admins with actionable insight. It is an internal
software developed at the University of Victoria by long-time members
of the syslog-ng community.

Writing syslog-ng Java destination drivers

If a destination is not supported by syslog-ng out of the box, you can
develop a new driver in C or one of the language bindings. Here are
the first steps for creating a Java-based destination driver:

Your feedback and news tips about the next issue is welcome at documentation(at)

Leave a Reply