public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Magnus Hagander <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Ronan Dunklau <[email protected]>
Cc: PostgreSQL Developers <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Subject: Re: Proposal: More structured logging
Date: Wed, 1 Sep 2021 09:35:19 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEy3F7ykNYnBcyvm_Dx7FP_ir9yOW9fTA7wz2bcTSG6Z=Q@mail.gmail.com>
References: <[email protected]>
<6062364.BDNAq9uPBk@aivenronan>
<[email protected]>
<CABUevEy3F7ykNYnBcyvm_Dx7FP_ir9yOW9fTA7wz2bcTSG6Z=Q@mail.gmail.com>
On 23.08.21 11:33, Magnus Hagander wrote:
> In short, I would also support the presence of JSON log format in
> core. (but as a proper log_destination of course -- or if it's time to
> actually split that into a separaet thing, being one parameter for
> log_destination and another for log_format)
It would be useful if there was some kind of standardized schema for
JSON logging, meaning what the keys should be named etc. Then we don't
need to make this all up from scratch, and there could be some
integration with existing log analysis tools.
view thread (19+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Proposal: More structured logging
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox