✓ No known CVEs patched in this version
Topics
+1 more
Summary
AI summaryYAML configuration, Azure Monitor output, and comprehensive hardening across modules.
Full changelog
rsyslog 8.2604.0
April 2026 scheduled-stable release.
Scheduled-stable releases are bi-monthly snapshots of the daily-stable branch, providing predictable update points with the same functional content as daily-stable at the time of the snapshot.
Highlights
- YAML as an alternative configuration format
- Azure Monitor output via
omazuredce - Gzip request compression for
omazuredce imhttpAPI key authentication- Native protobuf encoding for
omotelover HTTP - Broad hardening across queues, inputs, runtime behavior, and TLS
- Packaging, CI, and portability improvements
Notable changes
YAML configuration and policy workflows
.yamland.ymlfiles are now supported as a full alternative configuration format- YAML and RainerScript can coexist, enabling gradual adoption
mmjsontransformnow supports YAML policies for renaming or dropping JSON keys- YAML-backed ratelimit policies can be watched and reloaded with debounce support
- Shared
ratelimit.namesupport was extended across additional modules includingimrelp,omusrmsg,omfwd,omelasticsearch,omhttp,imhttp,imjournal,imklog, andimuxsock
Cloud, HTTP, and telemetry integration
- New Azure Monitor output support via
omazuredce - Gzip request compression for
omazuredce - Route-scoped API key authentication for
imhttp - Native protobuf encoding for
omotelviaprotocol="http/protobuf" - New
omfwdnum.connectsstatistic for TCP connection tracking
Reliability and security hardening
- Queue hardening, including follow-up fixes for corrupt disk queue recovery and startup issues
- Fix for a rare
imjournalcondition that could lead to a 100% CPU loop - Stronger
imtcpvalidation and worker shutdown handling - Bounded per-PID ratelimiter cache handling in
imuxsock - Safer payload length handling in
omhttp - Stable callback-state handling in
omrelp - GnuTLS CRL expiration is now enforced correctly
- Native post-quantum TLS guidance and tests
- DTLS builds now require explicit OpenSSL support when enabled
Build, CI, and portability
- RPM packaging overhaul and CI integration
- Rocky Linux 9 / EPEL 9 alignment for RPM CI
- Alpine compile checks
- musl resolver support for
omfwd - ARM CI improvements
- Initial deterministic unit-test plumbing
- Continued documentation and doc-build stabilization work
Compatibility notes
- For full 8.2604.0 functionality, build with
libyaml - YAML configuration support starts with rsyslog 8.2604.0
- DTLS modules require explicit OpenSSL support at build time
Contributors
Thanks to everyone who contributed to this release, including:
- Aditi Prakash
- anargam
- Attila Lakatos
- ca.mathieu
- Jan Kängsepp
- Marsel Mavletkulov
- Sagar Singh
- shinigami35
All other changes were contributed by Adiscon GmbH.
Full announcement
https://www.rsyslog.com/rsyslog-8-2604-0-yaml-configuration-azure-monitor-output-and-stronger-hardening/
Artifact availability
Source release artifacts are attached here.
Container images and distribution packages may appear with some delay after the release announcement as downstream publishing completes. This release page will be updated as those artifacts become available.
Release assets
This draft release includes the maintainer-built rsyslog-*.tar.gz source tarball produced by make dist.
These uploaded assets are the official source-release artifacts for this draft and are distinct from GitHub's auto-generated source snapshots.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Related context
Related tools
Beta — feedback welcome: [email protected]