JSON syslog output is not correctly cleaned

[JeremyEinfeld]

Csyslogd currently only strips quotes from json_safe_message, and ignores many other characters that are invalid in a JSON string. This often causes a failure to parse at the receiving end, most often encountered with Windows events (the use of a backslash in file paths creates invalid escape sequences and some event logs entries contain newlines and tabs).

Instead of stripping the characters, it should look for and escape (via backslash) any quotation marks, backslashes, tabs, or newlines (including the carriage return for messages from Windows agents).

[jrossi]

This is a known issue and thank you for raising a github issue about.

[jrossi]

If you have some time their is a pull request #2 that using a json libraray and generates json output via zeromq. This is gonna be the start to the new output framework, but might be something you can test out for now.

[reyjrar]

There's a pull request sitting with this patched, just need @jrossi to sanity check it.

[jrossi]

#49 accepted and this is in the mainline code