I'm taking syslog events from a proprietary app. This could be the app's fault or it could be rsyslogd.
Events are written like:
Aug 15 16:00:00 10.11.12.13 Event1 from this wonderful product using this odd Aug 15 16:01:00 10.11.12.13 format. Event2 from this wonderful product using Aug 15 16:02:00 10.11.12.13 this odd format. Event3 from this wonderful produ Aug 15 16:03:00 10.11.12.13 ct using this odd format.
you get the picture. Each record in syslog is ~2000 characters.
I'm not sure if this is an issue with the poorly defined nature of TCP syslog?
Does any expert on rsyslogd or syslog TCP have any advice as to where the problem might be? Is it likely that there's something I can do on the rsyslogd side to fix this? Or is this a normal mess for the state of TCP syslog?