On Sep 18, 2013, at 2:13 PM, Axel Rau <[email protected]> wrote: >> On Wed, 18 Sep 2013, David Lang wrote: >> >> I would suggest enhancing the control character escape handling to have a >> new option >> >> EscapeInfvalidUTF8 >> >> any byte sequences that are not valid UTF8 get changed to #nnn just like >> control characters. > This would help me a lot. >> >> This will allow people to paper over many of the problems and deal with >> senders that submit invalid UTF8 in the future. >> >> After this we can talk about conversion routines.
I had a similar situation a few months back trying to get json-formated rsyslog output (of Windows Event Logs forwarded from Snare) to be accepted by Logstash, and this solution (enhancing the control-character-escape handling) would have been perfectly fine with me too. No need to build the perfect solution to tag character sets to inputs when the log sources are going to lie anyway. -- Dave Caplinger, Director of Systems | 402.361.3063 Solutionary | Relevant . Intelligent . Security _______________________________________________ rsyslog mailing list http://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.
