Yes, you cannot detect many failures with UDP. RELP is the most reliable, but
getting it to failover to a second destination is more difficult (I think that
round-robin DNS will do it, but some testing would be needed)
see Rainer's post on the unreliability of TCP
All this being said, think hard about your actual reliability and delivery
latency requirements and the various failure modes you are trying to defend
against. You can spend a lot of time and effort defending against one rare case
and end up being vulnerable to loss from a much more common case.
David Lang
On Thu, 15 Oct
2020, Peter via rsyslog wrote:
Date: Thu, 15 Oct 2020 16:49:55 -0700 (MST)
From: Peter via rsyslog <[email protected]>
To: [email protected]
Cc: Peter <[email protected]>
Subject: Re: [rsyslog] Does anyone know how to configure log forwarding to a
multihomed host (with no log duplication)?
Ok thanks for the info. I assume that TCP would be required (as opposed to
UDP) so as to detect an undeliverable message? Or RELP?
--
Sent from: http://rsyslog-users.1305293.n2.nabble.com/
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
