Subject: Re: Proposal: More structured logging
To: Magnus Hagander <magnus@hagander.net>,
 Michael Paquier <michael@paquier.xyz>
Cc: Ronan Dunklau <ronan.dunklau@aiven.io>,
 PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>,
 Alvaro Herrera <alvherre@alvh.no-ip.org>
References: <202108191450.7vik45yrlwle@alvherre.pgsql>
 <6062364.BDNAq9uPBk@aivenronan> <YSBKT8kUMgssml3K@paquier.xyz>
 <CABUevEy3F7ykNYnBcyvm_Dx7FP_ir9yOW9fTA7wz2bcTSG6Z=Q@mail.gmail.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Message-ID: <982f9651-1607-d0bc-de85-c48a48952680@enterprisedb.com>
Date: Wed, 1 Sep 2021 09:35:19 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: 
 <CABUevEy3F7ykNYnBcyvm_Dx7FP_ir9yOW9fTA7wz2bcTSG6Z=Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/982f9651-1607-d0bc-de85-c48a48952680%40enterprisedb.com>
Precedence: bulk

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.