Logging format breaks structured logs

Can you provide more info on a system / use case for structured log data? From what I saw looking at monolog's JSON formatter, it would result in a stringified JSON (the violation report data) inside a JSON object (the log data's message attribute). Also complicated by the local endpoint name not being part of the violation report data, so the message isn't a clean JSON string even without the HTML.

The current module roadmap is to change from using the site log to storing reports in a dedicated database table. The storage manager could then be swapped out to send reports in the necessary format to whatever service you're using instead of to the database.
It's not currently planned to make that a plugin so you could implement a service to proxy violation reports to whichever service you use, but is a future possibility.

FWIW, I don't use this module, but right now I'm debugging an issue where using \

 in logging causes our log manager to break each line out into its own message, introducing a ton of noise and making it very hard to connect the thread between all the entries. This is using Acquia and Sumo Logic.

@charginghawk
sounds like syslog and newlines, rather than specifically pre?
This issue came up in the CSP module, which logs the same way: ✨ Add setting for pretty printing violoation reports in the log Active
and a related core issue: 📌 Sort out @backtrace_string logging by Syslog module Active
Not sure if the ini setting can be adjusted on Acquia

ini_set('syslog.filter', 'raw'); did end up resolving the issue for us.