Reliable Event Logging Protocol: Difference between revisions

Revision as of 14:11, 22 June 2013

Revision as of 09:25, 27 June 2013

Line 1:

'''Reliable Event Logging Protocol''' ('''RELP''') is a networking protocol for [[Computercomputer data logging]] in computer networks. It is based on the ideas of the [[syslog]] protocol but extends it to provide reliable delivery of event messages. It is most often used in environments where message loss is not acceptable, like in the financial industry.

==Overview==

Line 9:

While RELP was initially meant solely for rsyslog use, it became adopted more widely. Currently tools both under Linux and Windows support RELP. There are also in-house deployments for Java. While RELP is still not formally standardized, it has evolved into an industry standard for computer logging.

==Technical Detailsdetails==

RELP is inspired by RFC 3195 syslog and RFC 3080. During initial connection, sender and receiver negotiate session options, like supported command set or application level window size. Network event messages are transferred as commands, where the receiver acknowledges each command as soon as it has processed it. Sessions may be closed by both sender and receiver, but usually should be terminated by the sender side. In order to facilitate message recovery on session aborts, RELP keeps transaction numbers for each command, and negotiates which messages need to be resent on session reestablishment.

The current version of RELP does not specify native [[Transport Layer Security|TLS]] support. However, practical deployments use wrappers around the RELP session in order to provide that functionality.

==Implementations==