Comment 2 for bug 1786966

> I'm wondering whether we might want to adjust the errlog code to support the multiline input codec

Or maybe escaping is a better idea? We should probably be doing this anyway for non-printable characters.

Also, keeping to a single line gives (practical) compatibility with any tool which understands syslog

https://tools.ietf.org/html/rfc5424

eg. syslog-ng wants one line per message over tcp

https://github.com/balabit/syslog-ng/issues/1747