Well... I was too quick. The issue is that no matter what we do, we cannot simply log failed *tcp sends*. The reason is that actions fail some place inside the rule engine. At the point where it fails, it is unaware if it is a TCP send, file store, sql store, etc, etc, ... Of course the tcp output plugin can emit the failure message, but the tcp output plugin does not know if this is an ultimate failure or not - this depends on the rule engine configuration.
So if anything is set to report errors, you can either instrument the plugin and live with potentially false positives OR you can instrument the rule engine and generate messages in any instance (well, we could create an action-specific failure notice, which probably can be configured to what you exactly wanted to have - probably the solution...). In any case, feedback from your side is appreciated. Thanks, Rainer > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:rsyslog- > [EMAIL PROTECTED] On Behalf Of Rainer Gerhards > Sent: Monday, November 24, 2008 3:46 PM > To: rsyslog-users > Subject: Re: [rsyslog] Logging lost TCP connections > > OK, I will look into that, but I can not promise how trivial this may > be > ;) I keep you posted. > > Rainer > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:rsyslog- > > [EMAIL PROTECTED] On Behalf Of Pete Philips > > Sent: Monday, November 24, 2008 3:44 PM > > To: rsyslog-users > > Subject: Re: [rsyslog] Logging lost TCP connections > > > > Rainer Gerhards wrote: > > > Ummm... I was on the wrong side, checking the receiver. So you > would > > > like to log if the send does not succeed? > > > > Yes exactly. > > > > > Which brings up the question: do you have reasons for accepting the > > > message loss? I am asking because you can instruct rsyslog to retry > > > sending the data when the remote server is ready again. For an > > example, > > > see here: > > > > > > http://www.rsyslog.com/doc-rsyslog_reliable_forwarding.html > > > > I've seen that page and would like to use the disk buffering > capability > > of > > rsyslog to make logging failures unnecessary. Unfortunately the spec > > for the system > > I am delivering requires logging of failed delivery attempts and not > > disk > > buffering :-( > > > > > > Pete. > > -- > > Pete Philips > > Secerno Ltd > > Email: [EMAIL PROTECTED] > > PGP key: http://www.secerno.com/pgp/pete.gpg > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
