From d853a3f7cdff6f80fbfc45f7a9a7ab8209046884 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Tue, 1 Apr 2008 17:07:41 +0000 Subject: added im/omrelp doc --- doc/omrelp.html | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) create mode 100644 doc/omrelp.html (limited to 'doc/omrelp.html') 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