From: Ronan Dunklau <ronan.dunklau@aiven.io>
To: Magnus Hagander <magnus@hagander.net>
To: pgsql-hackers@lists.postgresql.org
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Michael Paquier <michael@paquier.xyz>
Subject: Re: Proposal: More structured logging
Date: Fri, 20 Aug 2021 11:35:29 +0200
Message-ID: <6062364.BDNAq9uPBk@aivenronan> (raw)
In-Reply-To: <202108191450.7vik45yrlwle@alvherre.pgsql>
References: <202108191450.7vik45yrlwle@alvherre.pgsql>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: ronan.dunklau@aiven.io, magnus@hagander.net, pgsql-hackers@lists.postgresql.org, alvherre@alvh.no-ip.org, michael@paquier.xyz
Subject: Re: Proposal: More structured logging
In-Reply-To: <6062364.BDNAq9uPBk@aivenronan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox