The #syslog_ng April newsletter is now available on-line:

- #Automatic configuration of the syslog-ng wildcard-file() source

- What to fix next in syslog-ng?

- #UDP #reliability improved in syslog-ng #Debian packaging

Read more at: https://www.syslog-ng.com/community/b/blog/posts/the-syslog-ng-insider-2026-04-wildcard-file-fix-udp

The syslog-ng Insider 2026-04: wildcard-file; fix; UDP

Dear syslog-ng users, This is the 139th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS Automatic configuration of the syslog-ng wildcard-file() source Reading files and monitoring directories became a l...

Why "#syslog_ng can do 7 million EPS" was announced on #AprilFoolsDay? It is a completely valid result. However, it was measured not in a #production, but in a #laboratory environment.

https://peter.czanik.hu/posts/new-toy-1st-of-april-syslog-ng-performance-tests/

So, it's an absolutely stunning result, just impossible in production.

My new toy: April 1 syslog-ng performance tests

Almost 15 years ago, Balabit had a campaign, stating that syslog-ng could process 650k messages a second. Now I am happy to present 7 million EPS (events per second). Timing the announcement to April 1 is not a coincidence :-) While the 650k EPS measurement was true, it was misleading. This value was measured right after syslog-ng 3.2 introduced multi-threading, in lab environment, under optimal circumstances, using synthetic log messages. However, there was no fine print explaining this, just the statement that syslog-ng could process 650k EPS.

Almost 15 years ago, Balabit had a campaign, stating that #syslog_ng could process 650k messages a second. Now I am happy to present 7 #million #EPS (events per second). Timing the announcement to April 1 is not a coincidence :-) #AprilFoolsDay

https://peter.czanik.hu/posts/new-toy-1st-of-april-syslog-ng-performance-tests/

My new toy: April 1 syslog-ng performance tests

Almost 15 years ago, Balabit had a campaign, stating that syslog-ng could process 650k messages a second. Now I am happy to present 7 million EPS (events per second). Timing the announcement to April 1 is not a coincidence :-) While the 650k EPS measurement was true, it was misleading. This value was measured right after syslog-ng 3.2 introduced multi-threading, in lab environment, under optimal circumstances, using synthetic log messages. However, there was no fine print explaining this, just the statement that syslog-ng could process 650k EPS.

I have an aging, but fully functional #MacBook, which I bought for #syslog_ng testing. @homebrew no more fully supports old, #Intel-based Macs. This blog helps to compile the latest syslog-ng release on these old, but otherwise functional machines.

https://www.syslog-ng.com/community/b/blog/posts/compiling-syslog-ng-on-an-old-mac

Compiling syslog-ng on an old Mac

I have an aging, but fully functional MacBook. I bought it for syslog-ng testing, but I also use for watching movies. Homebrew no more fully supports old, Intel-based Macs. This blog helps to compile the latest syslog-ng release on these old, but oth...

I love wearing #logowear: promotional t-shirts and other items, for products and projects I like. #syslog_ng, #IBM, #OneIdentity, @turris, @opensuse and many more. Yesterday I was at a #Solaris concert (not the operating system, but the #progrock band), and chose to wear something not IT-related. Imagine my surprise: other than some #music t-shirts, I have seen tons of IT-related clothing at this fantastic #concert 🙂

1/6

I'm investigating a regression that appeared after upgrading #OpenJDK in a setup where #syslog_ng communicates with a #Riemann server (a Java application).

My investigation led me to a C library (riemann-c-client, used by syslog-ng) that uses #GnuTLS to establish a mutually authenticated TLS connection to the Java service. The library provides a CLI utility that allows me to reproduce the problem, which suggests that the issue lies in this library rather than in syslog-ng itself.

The March #syslog_ng #newsletter is now on-line:

- Version 4.11.0 of syslog-ng is now available

- Using #OpenSearch data streams in syslog-ng

- Changes in the syslog-ng #Elasticsearch destination

It is available at https://www.syslog-ng.com/community/b/blog/posts/the-syslog-ng-insider-2026-03-4-11-0-release-opensearch-elasticsearch

The syslog-ng Insider 2026-03: 4.11.0 release; OpenSearch; ElasticSearch

Dear syslog-ng users, This is the 138th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS Version 4.11.0 of syslog-ng is now available Version 4.11.0 of syslog-ng is now available. The main attraction is ...

With a bit of delay, but #syslog_ng 4.11.0 is now available in @fedora #Rawhide. Support for #snmp is enabled again.

@opensuse I also updated the @fedora #Rawhide package, and according to the syslog-ng page on #repology, it's already there: https://repology.org/project/syslog-ng/versions

However, Rawhide still had #syslog_ng 4.10.2, when I checked a few minutes ago...

syslog-ng package versions - Repology

List of package versions for project syslog-ng in all repositories

Version 4.11.0 of syslog-ng was released last week, and it is already available in @opensuse #Tumbleweed!
#syslog_ng