Rsyslog has a modular design. Consequently, there is a growing
number of modules. See the HTML documentation for their full
description.
omsnmp SNMP trap output module
omgssapi
Output module for GSS-enabled syslog
ommysql
Output module for MySQL
omrelp Output module for the reliable RELP protocol (prevents
message loss). For details, see below at imrelp and the
HTML documentation. It can be used like this:
*.* :omrelp:server:port
*.* :omrelp:192.168.0.1:2514 # actual sample
ompgsql
Output module for PostgreSQL
omlibdbi
Generic database output module (Firebird/Interbase, MS
SQL, Sybase, SQLite, Ingres, Oracle, mSQL)
imfile Input module for text files
imudp Input plugin for UDP syslog. Replaces the deprecated -r
option. Can be used like this:
$ModLoad imudp
$UDPServerRun 514
imtcp Input plugin for plain TCP syslog. Replaces the deprecated
-t option. Can be used like this:
$ModLoad imtcp
$InputTCPServerRun 514
imrelp Input plugin for the RELP protocol. RELP can be used
instead of UDP or plain TCP syslog to provide reliable
delivery of syslog messages. Please note that plain TCP
syslog does NOT provide truly reliable delivery, with it
messages may be lost when there is a connection problem or
the server shuts down. RELP prevents message loss in
those cases. It can be used like this:
$ModLoad imrelp
$InputRELPServerRun 2514
imgssapi
Input plugin for plain TCP and GSS-enable syslog
immark Support for mark messages
imklog Kernel logging. To include kernel log messages, you need
to do
$ModLoad imklog
Please note that the klogd daemon is no longer necessary
and consequently no longer provided by the rsyslog
package.
imuxsock
Unix sockets, including the system log socket. You need to
specify
$ModLoad imuxsock
in order to receive log messages from local system
processes. This config directive should only left out if
you know exactly what you are doing.
