Rsyslog
Page Module:Infobox/styles.css has no content.
| Rsyslog | |
|---|---|
| [[Programmer|Original authorTemplate:Pluralize from text]] | Rainer Gerhards |
| Initial release | 2004 |
| Written in | C |
| Engine | Page Template:Plainlist/styles.css has no content.Template:EditAtWikidata |
| Operating system | Unix-like |
| Type | System logging |
| License | GNU General Public License v3 |
| Website | Lua error in package.lua at line 80: module 'Module:If preview' not found. |
| Repository | Page Template:Plainlist/styles.css has no content.
|
Script error: No such module "Check for conflicting parameters".
Rsyslog is an open-source software utility used on UNIX and Unix-like computer systems for forwarding log messages in an IP network. It implements the basic syslog protocol, extends it with content-based filtering, rich filtering capabilities, queued operations to handle offline outputs,[1] support for different module outputs,[2] flexible configuration options and adds features such as using TCP for transport.
The official RSYSLOG website defines the utility as "the Rocket-fast SYStem for LOG processing pipelines".[3]
Protocol
Rsyslog uses the standard BSD syslog protocol, specified in RFC 3164. As the text of RFC 3164 is an informational description and not a standard, various incompatible extensions of it emerged. Rsyslog supports many of these extensions. The format of relayed messages can be customized.
The most important extensions of the original protocol supported by rsyslog are:
- ISO 8601 timestamp with millisecond granularity and time zone information
- the addition of the name of relays in the host fields to make it possible to track the path a given message has traversed
- reliable transport using TCP
- support GSS-API and TLS
- logging directly into various database engines.
- support for RFC 5424, RFC 5425, RFC 5426
- support for RELP
- support for buffered operation modes where messages are buffered locally if the receiver is not ready
- complete input/output support for systemd journal
History
The rsyslog project began in 2004, when Rainer Gerhards, the primary author of rsyslog,[4] decided to write a new strong syslog daemon to compete with syslog-ng, because, according to the author, "A new major player will prevent monocultures and provide a rich freedom of choice."[5] Rainer Gerhards worked on rsyslog inside his own company, Adiscon GmbH.
Related RFCs and working groups
- RFC 3164 - The BSD syslog Protocol (obsoleted by RFC 5424)
- RFC 5424 - The Syslog Protocol (obsoletes RFC 3164)
- RFC 5425 - Transport Layer Security Mapping for Syslog
- RFC 5426 - Transmission of Syslog Messages over UDP
See also
Lua error in mw.title.lua at line 404: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal').
References
Page Template:Reflist/styles.css has no content.
- ^ Page Module:Citation/CS1/styles.css has no content."Rsyslog.conf(5) - Linux manual page".
- ^ Page Module:Citation/CS1/styles.css has no content."RSyslog Documentation".
- ^
Page Module:Citation/CS1/styles.css has no content."rsyslog". rsyslog.com. Retrieved 2025-10-30.
RSYSLOG is the rocket-fast system for log processing pipelines.
- ^ Page Module:Citation/CS1/styles.css has no content.Binnie, Chris (2016-11-30). "Remote Logging With Syslog, Part 1: The Basics". Linux.com. Retrieved 2025-11-25.
- ^ Page Module:Citation/CS1/styles.css has no content."Why does the world need another syslog?". August 12, 2007. Retrieved October 31, 2018.
External links
- Lua error in Module:Official_website at line 94: attempt to index field 'wikibase' (a nil value).
- rsyslog on GitHub
- Page Module:Citation/CS1/styles.css has no content."Rsyslog". Freecode.
