Re: [Json] Using JSON in log files

Bjoern Hoehrmann <derhoermi@gmx.net> Wed, 20 November 2013 17:02 UTC

Return-Path: <derhoermi@gmx.net>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2D51AE020 for <json@ietfa.amsl.com>; Wed, 20 Nov 2013 09:02:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level:
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SXtWo1OHv1Sm for <json@ietfa.amsl.com>; Wed, 20 Nov 2013 09:02:46 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 6436A1AE0B2 for <json@ietf.org>; Wed, 20 Nov 2013 09:02:46 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.33.37]) by mail.gmx.com (mrgmx102) with ESMTPA (Nemesis) id 0MXmpv-1WDcLo0tVP-00Wln5 for <json@ietf.org>; Wed, 20 Nov 2013 18:02:39 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Phillip Hallam-Baker <hallam@gmail.com>
Date: Wed, 20 Nov 2013 18:02:40 +0100
Message-ID: <g0qp8952rlt6j93estret25ushl8d1qf82@hive.bjoern.hoehrmann.de>
References: <CAMm+Lwj49w5qq3V8tLta_GPq3TT5A0FXuKww5RXHbe74dQ5jjA@mail.gmail.com>
In-Reply-To: <CAMm+Lwj49w5qq3V8tLta_GPq3TT5A0FXuKww5RXHbe74dQ5jjA@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:pA5usdbyW/es2DwehQfk+tIGxuGD17LIKu/r8KHCM+PKEYxyXyE dqRpvMDgycrqBhC2cEYNM+DvP9GmPB9NoXMAAY3hnFpbEfpzmIN9JnMKcLaw5yGId9R+oJP 3ShTDA7TZVd7kwTqTA+0LfXTTcWqqI1l+MflQym1yfeM8vD3EBebah0NTpJ3Q9Z/MQZ1n5u oiF+TwSmR84t0FI0AdCEA==
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] Using JSON in log files
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 17:02:48 -0000

* Phillip Hallam-Baker wrote:
>This is not an extension I would want to use in an on-the-wire format. But
>for log files it is essential. Particularly in my case where the logs are
>digitally signed notary records.

I use http://yaml.org/ for such purposes. It is a superset of JSON, in
a way. Converters to JSON, which you would need one way or another, are
readily available. You could also just cheat and say "It's JSON without
the encapsulating []".
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/