I'm using rsyslog v8.12 with liblognorm v3 experimental
I have control character escaping turned on in the global section, but I found
that if a string ends up having characters escaped like \r \n \t, and they get
parsed to a variable, when you output the variable, these are treated as JSON
escaped characters anc converted to CR newline, tab, etc
so I added :::escape-cc to my template, and I discovered that it's putting in
the wrong value
instead of \r becoming #015 it becomes #013, tab becomes #009 instead of #011
it looks like the escape-cc code is different from the
parser.escapeControlCharactersOnReceive="on" code and the escape-cc code is
putting in the decimal numbers instead of the octal numbers.
I was surprised to find that the property replacer was unescaping the \r values
inside a variable, but thinking about it, it makes sense (but I don't think it's
documented)
but the escape-cc thing is just a bug.
David Lang
_______________________________________________
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.
