Skip to content


Subversion checkout URL

You can clone with
Download ZIP
a Rocket-fast SYStem for LOG processing
C JavaScript Shell C++ Python Bison Other

travis: do not duplicate testing effort

reduce "make distcheck" to bare minumum until we can finally fix it.
That way, we still have the benefit of both the full testbench AND
make distcheck.
latest commit 3739e6c116
@rgerhards rgerhards authored
Failed to load latest commit information.
compat bugfix: build system strndup was used even if not present
contrib created param in add-flow to indicate if a graph being added to globa…
grammar Merge branch 'global_variable_atomicity' of…
m4 ax_check_define macro file was missed, added that
platform bugfix header in platform/redhat/rsyslog.conf
plugins Merge branch 'master' of into mas…
runtime bugfix imfile: regex multiline mode ignored escapeLF option
solaris added some more useful info to Solaris README
tests Merge branch 'fix-suspended-action' into master-candidate
tools maintain ChangeLog
.gitignore git-ignores a few files that get generated as a part of build/test runs
.travis.yml travis: enable "make dist" because "make distcheck" is still unreliable
AUTHORS cleaned up AUTHORS file and references updated note to developers according to policy change
COPYING changed license to GPLv3 (for what is to become rsyslog v3)
COPYING.ASL20 relicense parts under ASL 2.0
COPYING.LESSER changed some files to grant LGPLv3 extended persmissions on top of GPLv3
ChangeLog bugfix imfile: regex multiline mode ignored escapeLF option travis: do not duplicate testing effort
NEWS upgrading to autotools build system - thank Peter Vrabec for patches and
README fix file name change doc: some info on Ubuntu build requirements
action.c bugfix: action.ExecOnlyWhenPreviousIsSuspended does not work correctly
action.h Fixed race-condition in async-action that is to consume mutating mess… Use automake 1.11 silent-rules support testbench: proper cleanup
dirty.h add parameter -N3 to enable config check of partial config file
outchannel.c bugfix: prevent a double free
outchannel.h relicense parts under ASL 2.0
parse.c The AllowedSender directive misbehaved if network was down during sta…
parse.h cleanup: remove code for no-longer needed legacy conf functionality
pom.xml Add pom to package easily the java part with maven small systemd service file tweaks
sample.conf added a debugging template
syslog-tst.conf Initial revision
template.c cleanup
template.h Now that we have the ordinal day, we can easily get the week of the y…
threads.c fix build on non-Linux systems
threads.h better debug instrumentation --> input thread names used for reporting

Rsyslog - what is it?

Rsyslog is a rocket-fast system for log processing.

It offers high-performance, great security features and a modular design. While it started as a regular syslogd, rsyslog has evolved into a kind of swiss army knife of logging, being able to accept inputs from a wide variety of sources, transform them, and output to the results to diverse destinations.

Rsyslog can deliver over one million messages per second to local destinations when limited processing is applied (based on v7, December 2013). Even with remote destinations and more elaborate processing the performance is usually considered "stunning".

Mailing List

Installing rsyslog

Most distributions carry rsyslog in their repository. So you usually just need to use the package manager to install it. Note that on non-systemd systems (most notably Ubuntu), rsyslog usually is already installed.

Project-Provided Packages

Unfortunately, distributions often do not catch up with the pace of rsyslog development and as such only offer old versions. To solve that problem, we have created packages for current versions ourselves.

They are available for:

Building from Source

Follow the instructions at:

Build Environment .................

In general, you need

  • libestr
  • liblogging (stdlog component)

It is best to build these from source.

CentOS 6

for json-c, we need
  $ export PKG_CONFIG_PATH=/lib64/pkgconfig/

sudo yum install git valgrind autoconf automake flex bison python-docutils python-sphinx json-c-devel libuuid-devel libgcrypt-devel zlib-devel openssl-devel libcurl-devel gnutls-devel mysql-devel postgresql-devel libdbi-dbd-mysql libdbi-devel net-snmp-devel


Note: this list is (obviously) incomplete. We intend to complete it as we have more information and install additional systems.

sudo apt-get install libdbi-dev

openSUSE 13

sudo zypper install gcc make autoconf automake libtool libcurl-devel flex bison valgrind python-docutils libjson-devel uuid-devel libgcrypt-devel libgnutls-devel libmysqlclient-devel libdbi-devel libnet-devel postgresql-devel net-snmp-devellibuuid-devel libdbi-drivers-dbd-mysql

For the testbench VMs:

sudo zypper install gvim mutt

SUSE LINUX Enterprise Server 11

Available Packages: zypper install gcc make autoconf libtool flex bison

Missing Packages: libcurl-devel valgrind python-docutils uuid-devel libgcrypt-devel libgnutls-devel libmysqlclient-devel libdbi-devel postgresql-devel net-snmp-devel libdbi-drivers-dbd-mysql json-c zlib-dev libdbi

Reporting Bugs

Talk to the mailing list if you think something is a bug. Often, it's just a matter of doing some config trickery.

File bugs at:

How to Contribute

Contributions to rsyslog are very welcome. Fork and send us your Pull Requests.

For more information about contributing, see the CONTRIBUTING file.

Note that it is esay to add output plugins using languages like Python or Perl. So if you need to connect to a system which is not yet supported, you can easily do so via an external plugin. For more information see the README file in the external plugin directory.


The main rsyslog documentation is available in HTML format. To read it, point your web browser to ./doc/manual.html. Alternatively, you can view the documentation for the most recent rsyslog version online at:

Project Philosophy

We are an open source project in all aspects and very open to outside feedback and contribution. We base our work on standards and try to solve all real-world needs (of course, we occasionally fail tackeling actually all needs ;)). While the project is primarily sponsored by Adiscon, technical development is independent from company goals and most decisions are solely based on mailing list discussion results. There is an active community around rsyslog.

There is no such thing like being an official member of the rsyslog team. The closest to that is being subscribed to the mailing list:

This method of open discussions is modelled after the IETF process, which is probably the best-known and most successive collaborative standards body.

Project Funding

Rsyslog's main sponsor Adiscon tries to fund rsyslog by selling custom development and support contracts. Adiscon does NOT license rsyslog under a commercial license (this is simply impossible for anyone due to rsyslog's license structure).

Any third party is obviously also free to offer custom development, support and rsyslog consulting. We gladly merge results of such third-party work into the main repository (assuming it matches the few essential things written down in our contribution policy).

Something went wrong with that request. Please try again.