From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | David Arnold <dar(at)xoe(dot)solutions> |
Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Proposal: Adding json logging |
Date: | 2018-04-14 15:42:09 |
Message-ID: | 20180414154209.GI25709@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Apr 14, 2018 at 03:27:58PM +0000, David Arnold wrote:
> > Plus it's likely only a short-lived interchange format, not something to be
> retained for a long period.
>
> Absolutely.
>
> There might be an argument that it's not easy on the eyes in the case it
> would be consumed by a pair of them. It's absolutely valid. Golang
> community has found a solution for that called logfmt, which I personally
> appreciate.
I think a suite of json_to_* utilities would be a good bit more
helpful in this regard than changing our human-eye-consumable logs. We
already have human-eye-consumable logs by default. What we don't
have, and increasingly do want, is a log format that's really easy on
machines.
As to logfmt in particular, the fact that it's not standardized is
probably a show-stopper.
Let's go with JSON.
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-04-14 15:51:17 | Re: Proposal: Adding json logging |
Previous Message | Tom Lane | 2018-04-14 15:30:08 | Re: partitioning code reorganization |