| From: | Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: Proposal: More structured logging |
| Date: | 2021-08-20 09:35:29 |
| Message-ID: | 6062364.BDNAq9uPBk@aivenronan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le jeudi 19 août 2021, 16:50:10 CEST Alvaro Herrera a écrit :
> On 2021-Aug-19, Magnus Hagander wrote:
> > Another thing I've noticed in more and more other products is to be
> > able to log as json, which is then later thrown into a central logging
> > system somewhere. Basically like csv, but with the schema defined in
> > each row. Yes, a lot more overhead, but some systems really do like to
> > consume json.... So when we're on the topic of more structured
> > logging...
>
> Yeah, I was thinking in json logging too -- specifically thinking about
> Fluentbit and similar tools.
Michael, your jsonlog module already fullfills this need. Is it something that
should be merged into our tree ?
--
Ronan Dunklau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2021-08-20 10:36:02 | Re: Some leftovers of recent message cleanup? |
| Previous Message | Ronan Dunklau | 2021-08-20 09:31:21 | Re: Proposal: More structured logging |