Rsyslog is an enhanced multi-threaded syslogd with a focus on security and reliability. Among others, it offers support for on-demand disk buffering, reliable syslog over TCP, SSL, TLS and RELP, writing to databases (MySQL, PostgreSQL, Oracle, and many more), email alerting, fully configurable output formats (including high-precision timestamps), the ability to filter on any part of the syslog message, on-the-wire message compression, and the ability to convert text files to syslog. It is a drop-in replacement for stock syslogd and able to work with the same configuration file syntax.
Its advanced features make it suitable for enterprise-class, encryption protected syslog relay chains while at the same time being very easy to setup for the novice user. An optional web interface - phpLogCon - can be used to visualize all data online. In November 2007, rsyslog has become the default syslogd for the Fedora project.
rsyslog 3.22.1, a member of the v3-stable branch, has been released today. The release mainly consists of bugfixes like a fix for an invalid error message issued if $inlcudeConfig was on an empty set of files.
Hi all,
We have just released the new beta of rsyslog. This release consists of several enhancements like the added generic network stream server for syslog, capability to rebind the send socket of the UDP output section, a improved testbench with a config switch and some bugfixes. This release is recommended for all users of the beta branch.
Hi all,
We have released the first version of rsyslog v4-stable today. It is the next major step after v3 most importantly offering large performance improvements. This version went through a long beta-phase and we did not have any specifc bug reports within the last couple of weeks, so we honestly think this release is ready for production use.
we have just released rsyslog v5, an experimental version offering much better performance and an audit-grade queue system.
Yes - you have read right. We are actually now at v5 (in parallel to v4). For the time being, we will have both a v4-devel and a v5-devel.
Please see my blog post for details:
The v5 versions of rsyslog feature a greatly redesigned queue engine.The major theme for the v5 release is twofold:
a) greatly improved performance
b) enable audit-grade processing
Here, audit-grade processing means that rsyslog, if used together with audit-grade transports and configured correctly, will never lose messages that already have been acknowledged, not even in fatal failure cases like sudden loss of power.
Note that large parts of rsyslog's important core components have been restructured to support these design goals. As such, early versions of the engine will probably be less stable than the v3/v4 engine.
Also note that the initial versions do not cover all and everything. As usual, the code will evolve toward the final goal as version numbers increase.
Feedback is highly appreciated. If you have any bugs to report, I'd appreciate if you could do so via the rsyslog bugzilla:
today, we have released rsyslog 4.3.1, a member of the development branch. This version offers even greater performance for the imtcp input on multiprocessor machines. Also, multiple tcp listeners can now be defined. The build system and testbench have been enhanced, doc has been improved and there now is a capability to create a graphical representation of the rsyslog configuration. There are also some bug fixes included. This is a recommended update for all users of the devel branch.
rsyslog 4.1.7, now a member of the beta branch, has been released. This is the first incarnation o v4 flagged as beta. It offers all enhancements of v4. There have also been a number of bug fixes over 4.1.6, for example the fix for an invalid error check inside the PostgreSQL output module.
rsyslog 3.22.0, a member of the v3-stable branch, has been released today. This is the next and final iteration of v3-stable, bringing all the features of the previous beta branch. Among others, it provides enhanced performance, greater configurability and enhanced stability. This is the new v3-stable branch, retiring any previous versions. As such, it is a recommended update for all v3-stable users.
We have just released a brand-new 4.3.0 devel version, which starts the 4.3 series. It contains enhancements to RainerScript, an ever-improving testbench, and a new output plugin omprog. The later enables rsyslog to spawn an process that will receive log messages via stdin.
We have just released rsyslog 3.20.6, a member of the v3-stable branch. This is the last v3-stable for the 3.20.x series. The release mainly consists of bugfixes like a fix for an bug in $InputTCPMaxSessions which was accepted, but not executed, now resulting in a fixed upper limit of 200 connections. Further the default value of $DirCreateMode has been changed. For more information review the discussion on the mailing list: http://lists.adiscon.net/pipermail/rsyslog/2009-April/001986.html
we have just released rsyslog 2.0.7, a member of the v2-stable branch.
This is a bug-fixing release solving some minor bugs that were discovered during the past months. Most importantly, some issues with dynamically created files were fixed, as well as two memory leaks. While one of them was not expected to be seen in practice, there were one memory leak in the Postgres output module which could cause harm. This is a recommended update for all v2-stable users.
Other than on RHEL, 2.0.7 seems to be no longer used, but we still support it. So if you experience issues with that version, please let us know.
