From c5ae5472681c2fd594bb210c5794a83dbdc90eed Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Tue, 1 Apr 2008 16:46:04 +0000 Subject: preparing for 3.15.0 release --- doc/rsyslog_conf.html | 4 ++-- doc/status.html | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) (limited to 'doc') diff --git a/doc/rsyslog_conf.html b/doc/rsyslog_conf.html index 5931a241..2a0f0c60 100644 --- a/doc/rsyslog_conf.html +++ b/doc/rsyslog_conf.html @@ -26,7 +26,7 @@ number of modules. Here is the entry point to their documentation and what they do (list is currently not complete)

omsnmp - SNMP -trap output module
omrelp - RELP output module
omrelp - RELP output module
omgss - output module for GSS-enabled syslog
ommysql - output module for MySQL
ompgsql - output module for PostgreSQL
omrelp - RELP output module
imfile -- input module for text files
imrelp - RELP input module
imrelp - RELP input module
imudp - udp syslog message input
imtcp - input plugin for plain tcp syslog

rsyslog status page

This page reflects the status as of 2008-03-31.

This page reflects the status as of 2008-04-01.

Current Releases

development: 3.13.0-dev0 - -change log - -download

development: 3.15.0 - +change log - +download

If you updgrade from version 2, be sure to read the rsyslog v3 compatibility document.

Date: Tue, 1 Apr 2008 17:05:13 +0000 Subject: added forgotten files --- doc/imrelp.html | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++ doc/omrelp.html | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 106 insertions(+) create mode 100644 doc/imrelp.html create mode 100644 doc/omrelp.html (limited to 'doc') diff --git a/doc/imrelp.html b/doc/imrelp.html new file mode 100644 index 00000000..b6f1f2bc --- /dev/null +++ b/doc/imrelp.html @@ -0,0 +1,52 @@ + + +RELP Input Module + + + +

RELP Input Module

Module Name: imrelp

Author: Rainer Gerhards

Description:

Provides the ability to receive syslog messages via the +reliable RELP protocol. This module requires librelp to be +present on the system. From the user's point of view, imrelp works much +like imtcp or imgssapi, except that no message loss can occur. Please +note that with the currently supported relp protocol version, a minor +message duplication may occur if a network connection between the relp +client and relp server breaks after the client could successfully send +some messages but the server could not acknowledge them. The window of +opportunity is very slim, but in theory this is possible. Future +versions of RELP will prevent this. Please also note that rsyslogd may +lose a few messages if rsyslog is shutdown while a network conneciton +to the server is broken and could not yet be recovered. Future version +of RELP support in rsyslog will prevent that. Please note that both +scenarios also exists with plain tcp syslog. RELP, even with the small +nits outlined above, is a much more reliable solution than plain tcp +syslog and so it is highly suggested to use RELP instead of plain tcp. +Clients send messages to the RELP server via omrelp.

Configuration Directives:

InputRELPServerRun <port>
+Starts a RELP server on selected port

+Caveats/Known Bugs: +

see description

Sample:

This sets up a RELP server on port 2514.
+

+ +

[rsyslog.conf overview] +[manual index] [rsyslog site]

This documentation is part of the +rsyslog +project.
+Copyright © 2008 by Rainer +Gerhards and +Adiscon. +Released under the GNU GPL version 3 or higher.

+ \ No newline at end of file diff --git a/doc/omrelp.html b/doc/omrelp.html new file mode 100644 index 00000000..0952cc71 --- /dev/null +++ b/doc/omrelp.html @@ -0,0 +1,54 @@ + + +RELP Output Module (omrelp) + + + +

RELP Output Module (omlibdbi)

Module Name: omrelp

Author: Rainer Gerhards +<rgerhards@adiscon.com>

Description:

This module supports sending syslog messages over the reliable +RELP protocol. For RELP's advantages over plain tcp syslog, please see +the documentation for imrelp +(the server counterpart).

+Setup +

Please note the librelp +is required for imrelp (it provides the core relp protocol +implementation).

Configuration Directives:

This module uses old-style action configuration to keep +consistent with the forwarding rule. So far, no additional +configuration directives can be specified. To send a message via RELP, +use

*.* + :omrelp:<sever>:<port>;<template>

just as you use

*.* + @@<sever>:<port>;<template>

to forward a message via plain tcp syslog.

+Caveats/Known Bugs: +

See imrelp, +which documents them.

Sample:

The following sample sends all messages to the central server +"centralserv" at port 2514 (note that that server must run imrelp on +port 2514). Rsyslog's high-precision timestamp format is used, thus the +special "RSYSLOG_ForwardFormat" (case sensitive!) template is used.
+

+ +

[rsyslog.conf overview] +[manual index] [rsyslog site]

+ \ No newline at end of file -- cgit From ec089fb6add3536fe7cf5b5d790f75ca8ebfc058 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Wed, 2 Apr 2008 12:45:44 +0000 Subject: preparing for 3.14.0 release --- doc/status.html | 24 ++++++++++++++++-------- 1 file changed, 16 insertions(+), 8 deletions(-) (limited to 'doc') diff --git a/doc/status.html b/doc/status.html index c6901fb9..bfced290 100644 --- a/doc/status.html +++ b/doc/status.html @@ -2,18 +2,26 @@ rsyslog status page

rsyslog status page

This page reflects the status as of 2008-03-31.

This page reflects the status as of 2008-04-02.

Current Releases

development: 3.13.0-dev0 - -change log - -download

development: 3.15.0 - +change log - +download

+ +

v3 stable: 3.14.0 - change log - +download + +
v2 stable: 2.0.4 - change log - +download +
v0 and v1 are depricated and no longer supported. If you absolutely do not like to +upgrade, you may consider purchasing a +commercial rsyslog support package. Just let us point +out that it is really not a good idea to still run a v0 version. +

If you updgrade from version 2, be sure to read the rsyslog v3 compatibility document.

- -

stable: 2.0.4 - change log - -download

(How are versions named?)

Platforms

Thankfully, a number of folks have begin to build packages and -- cgit From 47bb1f0d1a0b99116f3864ac5e98e9ca8bb8e921 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Wed, 2 Apr 2008 13:13:12 +0000 Subject: updated status informatation and syslog-ng comparison --- doc/rsyslog_ng_comparison.html | 178 +++++++++++++++++++++++++---------------- doc/status.html | 16 +++- 2 files changed, 120 insertions(+), 74 deletions(-) (limited to 'doc') diff --git a/doc/rsyslog_ng_comparison.html b/doc/rsyslog_ng_comparison.html index 547501af..2a1d15bd 100644 --- a/doc/rsyslog_ng_comparison.html +++ b/doc/rsyslog_ng_comparison.html @@ -1,6 +1,8 @@ -rsyslog vs. syslog-ng - a comparison +rsyslog vs. syslog-ng - a comparison + +

rsyslog vs. syslog-ng

Written by Rainer Gerhards @@ -25,56 +27,72 @@ comparison sheet, so please don't be shy ;)

rsyslog syslog-ng - - -
Input Sources
+
+Input Sources
+ -UNIX domain socket + +UNIX domain socket +yes yes -yes - + + UDP yes -yes - +yes + + TCP yes -yes - +yes + + + +RELP +yes +no + + RFC 3195/BEEP yes (needs separate build process) -no - +no + + kernel log yes -yes - +yes + + file yes -yes - +yes + + -mark message generator as an optional input +mark message generator as an +optional input yes -no (?) - +no (?) + + Windows Event Log via EventReporter or MonitorWare Agent (both commercial software) -via separate Windows agent, paid edition only +via separate Windows agent, paid +edition only - - -
Network (Protocol) Support
+
+Network (Protocol) Support
+ support for (plain) tcp based syslog @@ -104,6 +122,11 @@ based framing on syslog/tcp connections yes +syslog over RELP
this is a truely reliable solution (plain tcp syslog can lose messages!) +yes +no + + on the wire (zlib) message compression yes @@ -146,38 +169,46 @@ hostname in NAT environments and relay chains yes yes - - -
Message Filtering
+
+Message Filtering
+ -Filtering for syslog facility and priority + +Filtering for syslog facility and +priority yes -yes - +yes + + Filtering for hostname yes -yes - +yes + + Filtering for application yes -yes - +yes + + Filtering for message contents yes -yes - +yes + + Filtering for sending IP address yes -yes - +yes + + -ability to filter on any other message -field not mentioned above +ability to filter on any other +message +field not mentioned above (including substrings and the like) yes no @@ -210,8 +241,9 @@ in filters support for discarding messages based on filters yes -yes - +yes + + powerful BSD-style hostname and program name blocks for easy multi-host support @@ -223,10 +255,10 @@ program name blocks for easy multi-host support - - -
Supported Database Outputs
+
+Supported Database Outputs
+ MySQL @@ -274,10 +306,10 @@ program name blocks for easy multi-host support yes (omlibdbi) no (?) - - -
Enterprise Features
+
+Enterprise Features
+ support for on-demand on-disk @@ -292,7 +324,8 @@ by spool files yes -each action can use its own, independant +each action can use its own, +independant set of spool files yes no @@ -314,10 +347,10 @@ syslog/database servers yes yes - - -
Config File
+
+Config File
+ config file format @@ -338,37 +371,40 @@ existing in a specific directory yes no - - - -
Extensibility
+
+Extensibility
+ -Functionality split in separately loadable +Functionality split in separately +loadable modules yes no -Support for third-party input plugins +Support for third-party input +plugins yes no -Support for third-party output plugins + +Support for third-party output +plugins yes no - - - -
Other Features
+
+Other Features
+ + + - ability to generate file names and directories (log targets) dynamically yes @@ -440,8 +476,9 @@ reduction ("last message repeated n times") on a per selector-line basis supports multiple actions per selector/filter condition yes -yes - +yes + + web interface phpLogCon
@@ -469,8 +506,11 @@ system stress flow control (slow down message reception when system is busy) -yes (advanced, with multiple ways to slow down inputs depending on individual input capabilities, based on watermarks) -yes (limited? "stops accepting messages") +yes (advanced, +with multiple ways to slow down inputs depending on individual input +capabilities, based on watermarks) +yes (limited? +"stops accepting messages") rewriting messages @@ -504,8 +544,6 @@ Solaris; compilation and basic testing done on HP UX no yes - -
While the rsyslog diff --git a/doc/status.html b/doc/status.html index c76fe348..b9bfd5c6 100644 --- a/doc/status.html +++ b/doc/status.html @@ -8,12 +8,20 @@
development: 3.15.0 - change log - download
+ +
v3 stable: 3.14.0 - change log - +download + +
v2 stable: 2.0.4 - change log - +download +
v0 and v1 are depricated and no longer supported. If you absolutely do not like to +upgrade, you may consider purchasing a +commercial rsyslog support package. Just let us point +out that it is really not a good idea to still run a v0 version. +
If you updgrade from version 2, be sure to read the rsyslog v3 compatibility document.
- -
stable: 2.0.4 - change log - -download
-
(How are versions named?)
+
(How are versions named?)

Platforms

Thankfully, a number of folks have begin to build packages and -- cgit From 10da14f1a80b83feaf048c7bfa608f680a6b11d4 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Fri, 4 Apr 2008 09:48:30 +0000 Subject: updating ... finally for release --- doc/status.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/status.html b/doc/status.html index bfced290..d7111a50 100644 --- a/doc/status.html +++ b/doc/status.html @@ -2,7 +2,7 @@ rsyslog status page
rsyslog status page
-
This page reflects the status as of 2008-04-02.
+
This page reflects the status as of 2008-04-04.

Current Releases

development: 3.15.0 - @@ -30,7 +30,7 @@ help port rsyslog to other platforms. As such, platform list is now maintained inside the rsyslog wiki. Platform maintainers perhaps have posted extra information there. If you do platform-specific work, feel free to add information to the wiki.
-
Rsyslog is the default syslogd in Fedora 8.
+
Rsyslog is the default syslogd in Fedora 8 and above.

Additional information

Currently supported features are listed on the rsyslog features page.

-- cgit