Hello RSyslog gurus!
I am trying to determine whether RSyslog can be configured to act as a
'translator' between a device that sends Syslog over TCP using the
'Octet-Counting' framing method (according to RFC 6587) to an
application/daemon that (currently) only supports the 'Non-Transparant
Framing' method (also RFC 6587 compliant, just minus Octet Counting
support.)
In addition, I would like the original (RFC 5424) Syslog Header to
remain intact, without rewriting or pre-pending an additional header -
i.e. it is only the 'framing' method that i need to adjust between
input/output.
Ideally, no local-disk store/log-file would be used - just a straight
TCP listener to an application/daemon running on the same host as
RSyslogD, either via UDP or TCP.
In RFC speak:
MUST receive Octet-Counting based framing over TCP
MUST send Non-Transparant Framing over TCP or UDP
SHOULD leave the original Syslog Header intact
SHOULD not pre-pend a new Syslog Header
MAY avoid any local disk/log-file storage
:-)
Thanks for any guidance you could offer - I have attempted to research
the question via the Archive and other online resources, but nothing
quite seems to match this use-case...
Martyn.
--
"There are 10 types of people in this world. Those who understand binary and those
who don't."
_______________________________________________
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.
