diff options
| author | Michael Biebl <biebl@debian.org> | 2008-03-29 12:14:24 +0100 |
|---|---|---|
| committer | Michael Biebl <biebl@debian.org> | 2008-03-29 12:14:24 +0100 |
| commit | ea79ad8dae160f0d0966b5a02fa3b73f0c3d1940 (patch) | |
| tree | 564de6e12a302f99754c7c8490b6dccd1292e70f /doc/features.html | |
| download | rsyslog-ea79ad8dae160f0d0966b5a02fa3b73f0c3d1940.tar.gz | |
Imported Upstream version 1.18.2upstream/1.18.2
Diffstat (limited to 'doc/features.html')
| -rw-r--r-- | doc/features.html | 80 |
1 files changed, 80 insertions, 0 deletions
diff --git a/doc/features.html b/doc/features.html new file mode 100644 index 0000000..725c3d7 --- /dev/null +++ b/doc/features.html @@ -0,0 +1,80 @@ +<html> +<head> +<title>rsyslog features</title> +</head> +<body> +<h1>RSyslog - Features</h1> +<p><b>This page lists both current features as well as those being considered +for future versions of rsyslog.</b> If you think a feature is missing, drop +<a href="mailto:rgerhards@adiscon.com">Rainer</a> a note. Rsyslog is a vital +project. Features are added each few days. If you would like to keep up of what +is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mailman/listinfo/rsyslog">rsyslog mailing list</a>. +</p> +<h2>Current Features</h2> +<ul> + + <li>native support for <a href="rsyslog_mysql.html">writing to MySQL databases</a><li>support for (plain) tcp + based syslog - much better reliability<li>support for sending and receiving + compressed syslog messages<li>ability to configure backup syslog/database + servers - if the primary fails, control is switched to a prioritized list of + backups<li>support for receiving messages via
reliable <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">
RFC 3195</a> delivery<li>ability to generate file names and directories (log targets) + dynamically, based on many different properties<li>control of log output format, + including ability to present channel and priority as visible log data<li>good timestamp format control; at a minimum, ISO 8601/RFC 3339 + second-resolution UTC zone<li>ability to reformat message contents and work with substrings<li>support for + log files larger than 2gb<li>support for file size limitation and automatic + rollover command execution<li>support for running multiple rsyslogd + instances on a single machine<li>support for <a href="rsyslog_stunnel.html"> + ssl-protected syslog</a> (via stunnel)<li>ability to filter on any part of + the message, not just facility and severity<li>ability to use regular + expressions in filters<li>support for discarding + messages based on filters<li>ability to execute shell scripts on received + messages<li>control of whether the local hostname or the hostname of the + origin of the data is shown as the hostname in the output<li>ability to + preserve the original hostname in NAT environments and relay chains + <li>ability to limit the allowed network senders<li>powerful BSD-style
hostname and program name blocks for easy multi-host support<li>
multi-threaded (<a href="http://rgerhards.blogspot.com/2007/08/why-is-rsyslog-multi-threaded-and-is-it.html">is + this important? why?</a>)<li>very
experimental and volatile support for <a href="syslog-protocol.html">syslog-protocol</a>
compliant messages (it is volatile because standardization is currently
underway and this is a proof-of-concept implementation to aid this effort)<li> + experimental support for syslog-transport-tls based framing on syslog/tcp + connections<li> + a copy of klogd.c has been included under the name of rklogd for those Linux + systems that need one. So rsyslog is a full replacement for the sysklogd + package<li> + support for IPv6<li> + ability to control repeated line reduction ("last message repeated n times") + on a per selector-line basis<li> + supports sub-configuration files, which can be automatically read from + directories. Includes are specified in the main configuration file<li> + supports multiple actions per selector/filter condition</ul> +<p> </p> +<h2>Upcoming Features</h2> +<p>The list below is something like a repository of ideas we'd like to +implement. Features on this list are typically NOT scheduled for immediate +inclusion. We maintain a +<a href="http://sourceforge.net/tracker/?group_id=123448&atid=696555">feature +request tracker at sourceforge.net</a>. This tracker has things typically within +reach of implementation. Users are encouraged to submit feature requests there +(or via our forums). If we like them but they look quite long-lived (aka "not +soon to be implemented"), they will possibly be migrated to this list here and +at some time moved back to the sourceforge tracker.</p> +<ul> + <li>create a plug-in-interface - we are very close to this. A neat interface is + already used internally for output modules.<li>implement native email-functionality in + selector (probably best done as a plug-in)<li>port it to more *nix variants + (eg AIX and HP UX) - this needs volunteers with access to those machines and + knowledge<li>provide an on-disk queue for syslog messages; should be + combined with reliable delivery to the next hop<li>support for native SSL enryption of plain tcp syslog sessions. This will + most probably happen based on syslog-transport-tls.<li>even more enhanced multi-threading, + with a message queue for each action (when implementing this, search + for CHECKMULTIQUEUE comments in the source - they already contain hints of + what to look at). Some detail information on this can already be found in + <a href="http://rgerhards.blogspot.com/2007/08/syslog-worker-pools-future-hardware-and.html"> + Rainer's blog</a>.<li>pcre filtering - maybe (depending on feedback) - simple regex already + partly added. So far, this seems sufficient so that there is no urgent need + to do pcre<li>support for
<a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a>
as a sender - this is currently unlikely to happen, because there is no real + demand for it. Any work on RFC 3195 has been suspend until we see some real + interest in it. It is probably much better to use TCP-based syslog, + which is interoprable with a large number of applications.</ul> +<p>To see when each feature was added, see the +<a href="http://www.rsyslog.com/Topic4.phtml">rsyslog change log</a> (online +only).</p> +</body> +</html> |