Agreed. Such a format would make log messages far more readable as well as making it easy for applications to parse them,
Nithya
----- Original Message -----
From: "Marcus Bointon" <marcus@xxxxxxxxxxxxxxxxxx>
To: "gluster-users" <gluster-users@xxxxxxxxxxx>, gluster-devel@xxxxxxxxxxx
Sent: Tuesday, 13 May, 2014 5:06:22 PM
Subject: Re: [Gluster-devel] GlusterFS and the logging framework
On 13 May 2014, at 13:30, Sahina Bose <sabose@xxxxxxxxxx> wrote:
> If the message was in a format:{"msgid":xxx,"msg": "Usage is above soft limit: 300.0KB used by /test/ ","volume": "test-vol", "dir":"/test"}
>
> This helps the applications that parse the logs to identify affected enitities. Otherwise we need to resort to pattern matching which is kinda flaky. (currently we monitor logs for a nagios monitoring plugin).
This is a great idea - Drupal does exactly this. If you use things like logstash, simple, reliable log formatting makes automated log processing much simpler.
Marcus
--
Marcus Bointon
Technical Director, Synchromedia Limited
Creators of http://www.smartmessages.net/
UK 1CRM solutions http://www.syniah.com/
marcus@xxxxxxxxxxxxxxxxxx | http://www.synchromedia.co.uk/
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
