Rsyslog is moving fast – let’s make sure everyone keeps up!

We are in “pushing new features out” mode since mid-2025. Observability Stack, Open Telemetry support, enhanced ETL tooling, centralized ratelimiters, CI improvements, AI components, much better doc, and, and and – a wealth of new features. Together with community contributors, that’s close to 900 commits. Big and small, some very big!

Please accept YouTube cookies to play this video. By accepting you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.

While doing this, I also wrote a lot these features and why they are there. But, guess what: the pace at which rsyslog currently moves is too fast for some rsyslog users. And especially those that run it, but think it is still just an good old syslogd.

To improve the situation, I have decided to focus a bit more on building awareness of the new features. Explain what they are and why they are good. You may call it a bit more of a doc and easy-to-use-method approach. This comes at the cost of somewhat less coding – but that’s not such a big deal, given what was already done.

We do not just need to do amazing things – we also need to tell folks these now exist and how they can use them!

So do not wonder if I may be more writing sentences than code in the next time. And: feel free to spread the good news about what rsyslog currently is – a high performance ETL tool and data pipeline component. And help us tell people how to use it.

Also help us by making it even easier to use! I am very grateful for all suggestions in this direction.