The new scheduled-stable release of rsyslog, version 8.2604.0 (2026.04), is now available. As the company behind rsyslog, Adiscon contributed a substantial portion of the engineering work in this cycle, including core implementation, release integration, documentation, packaging, CI, and related maintenance.
This scheduled-stable version is a bi-monthly snapshot of daily-stable and provides a predictable update point for operators. For full technical details, please refer to the full rsyslog 8.2604.0 release announcement on rsyslog.com.
Highlight 1: YAML configuration becomes a major new capability
The most visible Adiscon-led feature in this release is full YAML configuration support. rsyslog can now use .yaml and .yml files as a full alternative configuration format, while still allowing YAML and RainerScript to coexist in the same deployment.
Highlight 2: stronger hardening across the stack
A large portion of this release cycle focused on hardening across queues, runtime behavior, network inputs, TLS handling, packaging, and CI. This kind of integration and maintenance work is often less visible than a new feature, but it is central to how Adiscon helps keep rsyslog stable and production-ready over time.
Highlight 3: community features combined with Adiscon integration
rsyslog 8.2604.0 also combines important community contributions with substantial Adiscon integration work. Examples include the new Azure Monitor path via omazuredce, additional HTTP-facing capabilities, and broader observability improvements. This is a good example of how community development and Adiscon engineering reinforce each other.
You can learn more about this interplay in our article on open source and commercial development at Adiscon.
Full technical details
All module-level changes, fixes, compatibility notes, and contributor credits are available in the full rsyslog 8.2604.0 release announcement.
We thank everyone who contributed to this release — both Adiscon engineers and community contributors — for their work.