Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mGjNB-0004rW-Qs for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Aug 2021 14:50:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mGjNA-0006gj-RO for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Aug 2021 14:50:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mGjNA-0006gX-Jj for pgsql-hackers@lists.postgresql.org; Thu, 19 Aug 2021 14:50:24 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mGjN3-000344-Sk for pgsql-hackers@lists.postgresql.org; Thu, 19 Aug 2021 14:50:23 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 0304F3200A76; Thu, 19 Aug 2021 10:50:14 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 19 Aug 2021 10:50:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=P/qxhF+aD4ZByfmssYdq+3BvDrtTORL32eCli+oOxHE=; b=ZBj0t7gT fDkse9b4fUqrE16i0Jz0uMfvm1yUPufewrTauItL4OA8QinbolFKvKy3MA9prT/b fgn4lviDsldIogH5qSNHrOYZjrGN8nUzXgpfKhWJL48NUr0gxGRXF3IoTfW1cDKR qPSnb9R/xnR4jsrwio4RE5OomYl9oinCeJwAGESjGLRA3mT5nkkN2yWMRgyRR7w+ OcrEvZkJUtANo+nNDkkw2wPilt4nZp5pCkikLeFAfrMLdVtIha8zmBZpdNsryZHt pEz4r0U3xHmuFRqxQdquqN9rZYy2xLYNMSLMkvERB3MdLEYlzcMSbuYPaQU5Nst4 P49NWZveA4p8vw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrleejgdejlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgrrhho ucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgheqne cuggftrfgrthhtvghrnhepudejveejffejveduudetvdekieeuiedtvdeileefkeevjedu feeguedvjefhueelnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomhenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgv rhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Aug 2021 10:50:13 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 7BD042A062A; Thu, 19 Aug 2021 10:50:10 -0400 (-04) Date: Thu, 19 Aug 2021 10:50:10 -0400 From: Alvaro Herrera To: Magnus Hagander Cc: Ronan Dunklau , PostgreSQL Developers Subject: Re: Proposal: More structured logging Message-ID: <202108191450.7vik45yrlwle@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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/