Log consistently using Syslog over TCP about boulder

[grawity]

On the other hand, talking TCP directly means the program can't take advantage of various security & reliability features that dedicated syslog daemons (rsyslog, syslog-ng) already implement, like TLS encryption for the network forwarding...

[jcjones]

It does indeed. Preferably it should be configurable how we want to transmit the log data, though in my initial use case direct submission is the only practical way out of the jail.

[jcjones]

Due to some infrastructure changes, it's feasible now to reach rsyslog running on the host. I'm pretty tempted to discard the JSON-logging and instead use helper classes to serialize JSON whenever needed.

There is also a need for the helper to insert an easily-grok-able "AUDIT" flag of some sort to indicate that this message is to meet our CPS audit requirements, and thus be subject to extended retention.