Rsyslog Windows Agent 8.2 Released
A new version of the rsyslog Windows Agent is now available, version 8.2. This update delivers targeted stability improvements, performance optimizations for high-throughput environments, and enhanced compatibility with modern Windows operating systems.

Core Service & Engine Enhancements
High-Load Connection & Performance Optimizations
This release significantly improves the agent’s resilience under heavy traffic. Incoming TCP connections now benefit from an increased listen backlog and more reliable handling during connection spikes. Furthermore, timestamp processing across log messages is more reliable, backed by faster parsing for common log timestamp formats. Rule search expression evaluation has also been optimized for greater speed, accompanied by updated documentation.
Stability & Message Handling
Filter rule evaluation has been stabilized to resolve edge-case issues during message processing. Output formatting logic has been refined to ensure predictable message content preparation prior to forwarding or storage. In addition, character set conversions are now clearer and more consistent across operations.
Operating System Compatibility & Diagnostics
Configuration validation has been tightened to ensure reliable loading of configuration version details. Windows Event Log handling has been updated to ensure event category names render correctly on modern operating systems, including Windows 11 and Windows Server 2025. Finally, diagnostic and debug error messages now display correctly across all supported languages and character encodings.
Download
The new release is available for immediate download through the official page:
RSyslog Windows Agent 8.1 Released
Release Date: 2025-07-16
Build-IDs: Service 8.1.0.232, Client 8.1.0.321
RSyslog Windows Agent 8.0 Released
Release Date: 2025-01-23
Build-IDs: Service 8.0.0.230, Client 8.0.0.320
Enhancements |
|
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 7.2 Released
Release Date: 2022-01-18
Build-IDs: Service 7.2.0.217, Client 7.2.0.310
Features |
|
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 7.1 Released
Release Date: 2021-07-14
Build-IDs: Service 7.1.0.214, Client 7.1.0.300
Features |
|
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 6.2d Released
Release Date: 2021-02-19
Build-IDs: Service 6.2.0.211, Client 6.2.0.284
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 6.2c Released
Release Date: 2021-01-28
Build-IDs: Service 6.2.0.210, Client 6.2.0.284
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 6.1 Released
Release Date: 2020-01-31
Build-IDs: Service 6.1.0.205, Client 6.1.0.280
Features |
|
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 5.1 Released
Release Date: 2018-08-23
Build-IDs: Service 5.1.0.193, Client 5.1.0.269
Features |
|
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
Version support policy change
We will be changing our policy so that only the latest stable build will be officially supported. This is done in an effort to concentrate resouces on building new and great things, instead of wasting a lot of time merging from old versions. A lot of -competing- projects have this policy and thus can move faster. We don’t want to carry that disadvantage any further with us.
For folks with support contracts, of course nothing changes: we always supported all versions – no matter how old – under these contracts (as long as technically possible). Please also note that we always consider older, but frequently used versions when it comes to important bug fixes (for example, I lately added a couple of fixes to v5.10, which is no longer officially supported for quite a while).
I would like to point out that rsyslog has a very considerate version management, with keeping major versions in different branches and (via professional support) taking care of each old version. This enterprise release scheme is under no discussion.
As a side-note: the discussion was started when I thought about non-critical fixes that I did for v7 and we thought about if it really makes sense to spend time to backport them to v6. There are also some enhancement-like “bugfixes” (like better config error messages), which will stay with the devel branch and mature into the next stable (if for nothing else, than for their regression potential).
Best regards,
Rainer Gerhards
