Content deleted Content added
m Dating maintenance tags: {{Citation needed}} |
|||
(4 intermediate revisions by 4 users not shown) | |||
Line 1:
'''Reliable Event Logging Protocol''' ('''RELP''')
==Overview==
RELP uses [[Transmission Control Protocol|TCP]] for message transmission. This provides basic protection against message loss, but does not guarantee delivery under all circumstances. When a connection
{{cite web |url=http://blog.gerhards.net/2008/05/why-you-cant-build-reliable-tcp.html |date=2008-05-29 |title=Why you can't build a reliable TCP protocol without app-level acks |accessdate=2013-05-06 }} </ref> Unlike the syslog protocol, RELP works with a [[backchannel ==History==
Line 17 ⟶ 25:
Only publicly available implementations are listed. This list is not exhaustive.
* [https://www.rsyslog.com/librelp/ librelp] - the original C RELP library
* [[rsyslog]]
* MonitorWare (Windows)
* [http://logstash.net logstash]
* [https://github.com/teragrep/rlp_01 rlp_01] - Java RELP Library
* [https://github.com/teragrep/jla_01 jla_01] - RELP Logback Plugin
* [https://github.com/teragrep/jla_04 jla_04] - Java Util Logging RELP Handler
* [https://github.com/teragrep/jla_05 jla_05] - Log4j RELP Plugin
==References==
|