On Sun, Apr 15, 2018 at 10:39 AM, David Arnold <email@example.com> wrote:
> >More specifically, JSON logging does seem to be a solution in search of a
> problem. PostgreSQL's CSV logs are very easy to machine-parse, and if
> there are corrupt lines being emitted there, the first step should be to
> fix those, rather than introduce a new "this time, for sure" logging method.
> >It's a matter of a few lines of code to convert CSV logs to a JSON
> format, if you need JSON format for something else.
> In the light of the specific use case / problem for this thread to be
> born, what exactly would you suggest?
This would appear to solve multiline issues within Fluent.....