| From: | John W Higgins <wishdev(at)gmail(dot)com> |
|---|---|
| To: | David Arnold <dar(at)xoe(dot)solutions> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Proposal: Adding json logging |
| Date: | 2018-04-15 17:58:24 |
| Message-ID: | CAPhAwGxo9g3nuu7mONeZAWMt+oNHrY+OnLE46Mka0b-3JnBv_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 15, 2018 at 10:39 AM, David Arnold <dar(at)xoe(dot)solutions> 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.....
https://docs.fluentd.org/v0.12/articles/parser_multiline
John
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Arnold | 2018-04-15 18:00:05 | Re: Proposal: Adding json logging |
| Previous Message | Christophe Pettus | 2018-04-15 17:46:01 | Re: Proposal: Adding json logging |