You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Michael Biebl 0bdc3cb661 Release version 8.31.0-2 to unstable 2 years ago
compat New upstream version 8.31.0 2 years ago
contrib New upstream version 8.31.0 2 years ago
debian Release version 8.31.0-2 to unstable 2 years ago
grammar New upstream version 8.31.0 2 years ago
m4 New upstream version 8.23.0 3 years ago
platform Imported Upstream version 8.8.0 5 years ago
plugins New upstream version 8.31.0 2 years ago
runtime New upstream version 8.31.0 2 years ago
tests New upstream version 8.31.0 2 years ago
tools New upstream version 8.31.0 2 years ago
.tarball-version New upstream version 8.31.0 2 years ago
AUTHORS Imported Upstream version 5.7.0 9 years ago
CONTRIBUTING.md New upstream version 8.24.0 3 years ago
COPYING Imported Upstream version 3.14.1 12 years ago
COPYING.ASL20 Imported Upstream version 5.8.8 8 years ago
COPYING.LESSER Imported Upstream version 3.16.1 12 years ago
ChangeLog New upstream version 8.31.0 2 years ago
INSTALL Imported Upstream version 8.6.0 5 years ago
Makefile.am New upstream version 8.29.0 2 years ago
Makefile.in New upstream version 8.31.0 2 years ago
NEWS Imported Upstream version 1.18.2 12 years ago
README Imported Upstream version 8.2.0 6 years ago
README.md New upstream version 8.27.0 3 years ago
aclocal.m4 New upstream version 8.23.0 3 years ago
action.c New upstream version 8.31.0 2 years ago
action.h New upstream version 8.25.0 3 years ago
compile Imported Upstream version 8.19.0 4 years ago
config.guess New upstream version 8.23.0 3 years ago
config.h.in New upstream version 8.31.0 2 years ago
config.sub New upstream version 8.23.0 3 years ago
configure New upstream version 8.31.0 2 years ago
configure.ac New upstream version 8.31.0 2 years ago
depcomp Imported Upstream version 8.19.0 4 years ago
dirty.h New upstream version 8.31.0 2 years ago
install-sh New upstream version 8.23.0 3 years ago
ltmain.sh New upstream version 8.23.0 3 years ago
missing Imported Upstream version 8.19.0 4 years ago
outchannel.c New upstream version 8.23.0 3 years ago
outchannel.h Imported Upstream version 5.8.7 8 years ago
parse.c New upstream version 8.31.0 2 years ago
parse.h New upstream version 8.25.0 3 years ago
rsyslog.service.in Imported Upstream version 8.4.1 5 years ago
template.c New upstream version 8.31.0 2 years ago
template.h New upstream version 8.31.0 2 years ago
test-driver Imported Upstream version 8.19.0 4 years ago
threads.c New upstream version 8.31.0 2 years ago
threads.h Imported Upstream version 7.1.9 7 years ago
ylwrap Imported Upstream version 8.19.0 4 years ago

README.md

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

http://lists.adiscon.net/mailman/listinfo/rsyslog

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: http://www.rsyslog.com/doc/build_from_repo.html

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

Ubuntu

Add Adiscon repository:

apt-get update && apt-get install -y software-properties-common
add-apt-repository -y ppa:adiscon/v8-stable

Note: if you are a developer who wants to work with git master branch, adding the Adiscon repository is probably not a good idea. It then is better to also compile the supporting libraries from source, because newer versions of rsyslog may need newer versions of the libraries than there are in the repositories. Libraries in question are at least: libestr, liblognorm, libfastjson.

Needed packages to build with omhiredis support:

apt-get update && apt-get install -y build-essential pkg-config libestr-dev libfastjson-dev zlib1g-dev uuid-dev libgcrypt20-dev liblogging-stdlog-dev libhiredis-dev uuid-dev libgcrypt11-dev liblogging-stdlog-dev flex bison

Aditional packages for other modules:

libdbi-dev libmysqlclient-dev postgresql-client libpq-dev libnet-dev librdkafka-dev libgrok-dev libgrok1 libgrok-dev libpcre3-dev libtokyocabinet-dev libglib2.0-dev libmongo-client-dev  

For KSI, from the Adiscon PPA:

sudo apt-get install libksi0 libksi-devel

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: https://github.com/rsyslog/rsyslog/issues

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 easy 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.

Documentation

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: http://www.rsyslog.com/doc

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 tackling 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: http://lists.adiscon.net/mailman/listinfo/rsyslog

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).