Re: Proposal: Adding json logging

This discussion is thriving, and long and behold, we've got an opinion from Eduardo (fluent-bit):

https://github.com/fluent/fluent-bit/issues/564#issuecomment-381844419

>Also consider that in not all scenarios full multiline logs are flushed right away, sometimes there are delays.

I think this line supports the view for multi line being a sub optimal logging strategy (assessed globally and embedded into an deployment ecosystem).

> Btw, we would be happy to work together with PostreSQL community to support an official parser for your multiline logs

Although, fluent-bit seem to strive to work with postgres log "as it pleases", I think it is still a valid problem definition against all contrary arguments to maintain:

Core-Problem: "Multi line logs are unnecessarily inconvenient to parse and are not compatible with the design of some (commonly used) logging aggregation flows."
2nd-order Problem: "Logging space increasingly moves towards the adoption of structured logging formats around json/logfmt. Compatibly options (plural!) with main stream (not necessarily standard) tooling is a value proposition of it's own kind. It helps increase odds of responsible deployments and improves the overall experience in adopting PostgreSQL."

Please share you thoughts, if you still feel there are material objections to the core problem? JSON or not JSON, as Christophe recalled, then is a question in the solution space.