17.12.2013 12:31, Rainer Gerhards:
Folks,
I could need a bit of technical advise. There is a problem with the way
logger /imuxsock work and JSON escaping. The details are here:
http://kb.monitorware.com/post24048.html
Feedback appreciated, I'd like to settle this within the next two days ;)
Frankfully, I do not understand what topic starter wants to do.
The template:
template(name="plain_syslog" type="list") {
constant(value="{")
property(name="msg" format="json")
constant(value="\"}")
constant(value="\n")
}
It should output something in curly braces, yes? Something alike to JSON
container? Why there is an unpaired double quote, by the way?
What it does now?
What is it supposed to output?
The above results in 'there is a \\n in here'
So where are those curly braces? What is the real output?
My feeling is that logger is not supposed to allow escaped characters to
be passed to it's input. It does not decode anything. So, if JSON needs
to escape those slashes - this is the right behaviour.
--
Pavel Levshin
_______________________________________________
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.
