English Français Español

History of rsyslog

Last update Mar. 20^th 2013 5:56:58 PM

Creation date Mar. 19^th 2013 7:13:35 PM

miceno on Mar. 20^th 2013 5:56:58 PM
Latest version
7.2.6 stable (March 2013)
miceno on Mar. 20^th 2013 4:26:02 PM
ability to execute shell scripts on received messages
yes
DNS cache
yes
miceno on Mar. 20^th 2013 4:10:57 PM
support for TLS/SSL-protected syslog
yes (since 3.19.0)via stunnel
Windows Event Log
yes a Windows event logging software such as EventReporter orMonitorWare Agent (both commercial software, both fund rsyslogdevelopment)
miceno on Mar. 19^th 2013 7:15:10 PM
Editor
public
Viewer
public
miceno on Mar. 19^th 2013 7:13:35 PM
Mode
70
Name
rsyslog
Viewer
unlisted
Editor
miceno-1km2vspw
Category
it-development
Website
http://www.rsyslog.com
license
GPLv3 (GPLv2 for v2 branch)
UNIX domain socket
yes
UDP
yes
TCP
yes
RELP
yes
RFC 3195/BEEP
yes (via im3195)
kernel log
yes
file
yes
mark message generator as an optional input
yes
Windows Event Log
via a Windows event logging software such as EventReporter or MonitorWare Agent (both commercial software, both fund rsyslog development)
support for (plain) tcp based syslog
yes
support for GSS-API
yes
ability to limit the allowed network senders (syslog ACLs)
yes
support for syslog-transport-tls based framing on syslog/tcp connections
yes
udp syslog
yes
syslog over RELP
yes
truly reliable message delivery (Why is plain tcp syslog not reliable?)
yes
on the wire (zlib) message compression
yes
support for receiving messages via reliable RFC 3195 delivery
yes
support for TLS/SSL-protected syslog
natively (since 3.19.0)
via stunnel
support for IETF's new syslog-protocol draft
yes
support for IETF's new syslog-transport-tls draft
yes (since 3.19.0 - world's first implementation)
support for IPv6
yes
native ability to send SNMP traps
yes
ability to preserve the original hostname in NAT environments and relay chains
yes
Filtering for syslog facility and priority
yes
Filtering for hostname
yes
Filtering for application
yes
Filtering for message contents
yes
Filtering for sending IP address
yes
ability to filter on any other message field not mentioned above (including substrings and the like)
yes
support for complex filters, using full boolean algebra with and/or/not operators and parenthesis
yes
support for arbritrary complex arithmetic and string expressions inside filters
yes
ability to use regular expressions in filters
yes
support for discarding messages based on filters
yes
ability to filter out messages based on sequence of appearing
yes (starting with 3.21.3)
powerful BSD-style hostname and program name blocks for easy multi-host support
yes
MySQL
yes (native ommysql, omlibdbi)
PostgreSQL
yes (native ompgsql, omlibdbi)
Oracle
yes (omlibdbi)
SQLite
yes (omlibdbi)
Microsoft SQL (Open TDS)
yes (omlibdbi)
Sybase (Open TDS)
yes (omlibdbi)
Firebird/Interbase
yes (omlibdbi)
Ingres
yes (omlibdbi)
mSQL
yes (omlibdbi)
support for on-demand on-disk spooling of messages
yes
ability to limit disk space used by spool files
yes
each action can use its own, independant set of spool files
yes
different sets of spool files can be placed on different disk
yes
ability to process spooled messages only during a configured timeframe (e.g. only during off-peak hours, during peak hours they are enqueued only)
yes (can independently be configured for the main queue and each action queue)
ability to configure backup syslog/database servers
yes
Professional Support
yes
config file format
compatible to legacy syslogd but ugly
ability to include config file from within other config files
yes
ability to include all config files existing in a specific directory
yes
Functionality split in separately loadable modules
yes
Support for third-party input plugins
yes
Support for third-party output plugins
yes
ability to generate file names and directories (log targets) dynamically
yes
control of log output format, including ability to present channel and priority as visible log data
yes
native ability to send mail messages
yes (ommail, introduced in 3.17.0)
good timestamp format control; at a minimum, ISO 8601/RFC 3339 second-resolution UTC zone
yes
ability to reformat message contents and work with substrings
yes
support for log files larger than 2gb
yes
support for log file size limitation and automatic rollover command execution
yes
support for running multiple syslogd instances on a single machine
yes
massively multi-threaded for tomorrow's multi-core machines
yes
ability to control repeated line reduction ("last message repeated n times") on a per selector-line basis
yes
supports multiple actions per selector/filter condition
yes
web interface
phpLogCon [also works with php-syslog-ng]
using text files as input source
yes
rate-limiting output actions
yes
discard low-priority messages under system stress
yes
flow control (slow down message reception when system is busy)
yes (advanced, multiple ways to slow down inputs depending on individual input capabilities, based on watermarks)
rewriting messages
yes
output data into various formats
yes
ability to control "message repeated n times" generation
yes

Go back to: rsyslog