[syslog-ng] Insider 2021-05: 3.32; Fortigate; Windows event collector; FreeBSD; Pi;

Peter Czanik (pczanik) Peter.Czanik at oneidentity.com
Thu May 13 10:09:58 UTC 2021


Dear syslog-ng users,

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

NEWS

syslog-ng 3.32 is now available
-------------------------------
Highlights include multi-threaded connection pooling to MongoDB servers and template support for its collection() option. OpenBSD support is now fixed. For a complete list of changes, check the release notes at:
https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-3.32.1

Parsing Fortigate logs and other syslog-ng 3.31 news
----------------------------------------------------
Version 3.31 of syslog-ng has been released recently. One of its most user-visible features is the parser for Fortigate logs, yet another networking vendor that produces log messages not conforming to syslog specifications. Parsing Fortigate logs builds upon the new no-header flag of syslog-ng combined with the key-value and date parsers. Other features include a new silent message option for the Telegram destination and automatic directory creation for disk-buffer files.
https://www.syslog-ng.com/community/b/blog/posts/parsing-fortigate-logs-and-other-syslog-ng-3-31-news

Collecting Windows EventLog without installing extra software on Windows
--------------------------------------------
Talking to users at both IT security and operations related conferences, they confessed the same: the less software the better. Less software to learn, maintain and follow in bug trackers. The Windows Event Collector (WEC) component of syslog-ng Premium Edition (PE) brings this to the extremes: it enables Windows machines to act as log sources without installing any software. Just enable the WEC component of syslog-ng PE on your Linux server and enjoy the logs flowing in. From this blog you can learn how to set up a test environment for WEC. I will also show you an easier way to prepare the certificates used, help you avoid some of the failures, and point you to alternative ways, where necessary.
https://www.syslog-ng.com/community/b/blog/posts/windows-event-collector-forwarding-syslog_2d00_ng

syslog-ng on the FreeBSD wiki
-----------------------------
My original blog about getting started with syslog-ng on FreeBSD became outdated. The content was updated and extended a bit, and with some help from the FreeBSD community, it is now available on the FreeBSD wiki at https://wiki.freebsd.org/Ports/sysutils/syslog-ng

Syslog-ng & Pi day
------------------
We had March 14th recently, or as many geeks refer to it: Pi day. On this occasion, I would like to show you a syslog-ng configuration, which prints a huge π on the screen, and two recent articles that feature syslog-ng on the Raspberry Pi.
https://www.syslog-ng.com/community/b/blog/posts/syslog-ng-pi-day

WEBINARS

* syslog-ng, Swiss Army Knife of Log Management: https://www.syslog-ng.com/event/syslogng-swiss-army-knife-of-log-management8148852/
* You can browse recordings of past webinars at https://www.syslog-ng.com/events/

Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/


Peter Czanik (CzP) <peter.czanik at oneidentity.com>
Balabit (a OneIdentity company) / syslog-ng upstream
https://syslog-ng.com/community/
https://twitter.com/PCzanik







More information about the syslog-ng mailing list