You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2015/03/13 21:45:38 UTC

[jira] [Commented] (SAMZA-597) Support a JSON encoder for Log4J StreamAppender

    [ https://issues.apache.org/jira/browse/SAMZA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361057#comment-14361057 ] 

Yi Pan (Data Infrastructure) commented on SAMZA-597:
----------------------------------------------------

+1. LGTM.

> Support a JSON encoder for Log4J StreamAppender
> -----------------------------------------------
>
>                 Key: SAMZA-597
>                 URL: https://issues.apache.org/jira/browse/SAMZA-597
>             Project: Samza
>          Issue Type: Bug
>          Components: log4j
>    Affects Versions: 0.9.0
>            Reporter: Chris Riccomini
>            Assignee: Chris Riccomini
>             Fix For: 0.9.0
>
>         Attachments: SAMZA-597-0.patch, SAMZA-597-1.patch
>
>
> We are trying to hook a Samza job up to [ELK|https://www.digitalocean.com/community/tutorials/how-to-use-logstash-and-kibana-to-centralize-and-visualize-logs-on-ubuntu-14-04]. During this exercise, I found that the only format available is a String-encoded LoggingEvent. Logstash has a [well-defined|https://github.com/logstash/log4j-jsonevent-layout] LoggingEvent JSON encoding. It would be nice if Samza supported this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)