Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 12 Oct 2011 15:21:12 +0000 (UTC)
From: "Steve Loughran (Updated) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1872278727.5413.1318432872068.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <425371438.11599.1317394785684.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-7705) Add a log4j back end that can push
 out JSON data, one per line
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HADOOP-7705:
-----------------------------------

    Status: Open  (was: Patch Available)
    
> Add a log4j back end that can push out JSON data, one per line
> --------------------------------------------------------------
>
>                 Key: HADOOP-7705
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7705
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: util
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-7705-log4json.patch, HADOOP-7705.patch
>
>
> If we had a back end for Log4j that pushed out log events in single line JSON content, we'd have something that is fairly straightforward to machine parse. If: it may be harder to do than expected. Once working HADOOP-6244 could use it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira