| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Proposal: More structured logging |
| Date: | 2021-08-19 14:50:10 |
| Message-ID: | 202108191450.7vik45yrlwle@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2021-08-19 15:40:44 | Re: Allow declaration after statement and reformat code to use it |
| Previous Message | Tom Lane | 2021-08-19 14:34:04 | Re: Allow declaration after statement and reformat code to use it |