[jira] [Updated] (SAMZA-919) Add milliseconds and thread name to log4j configs.

["Jake Maes (JIRA)" <ji...@apache.org>]

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

Jake Maes updated SAMZA-919:
----------------------------
    Attachment: SAMZA-919_hello-samza.patch
                SAMZA-919_samza.patch

Samza
  Patch: SAMZA-919_samza.patch
  RB: https://reviews.apache.org/r/45388/

Hello Samza
  Patch: SAMZA-919_hello-samza.patch
  RB: https://reviews.apache.org/r/45387/

> Add milliseconds and thread name to log4j configs. 
> ---------------------------------------------------
>
>                 Key: SAMZA-919
>                 URL: https://issues.apache.org/jira/browse/SAMZA-919
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jake Maes
>            Assignee: Jake Maes
>             Fix For: 0.10.1
>
>         Attachments: SAMZA-919_hello-samza.patch, SAMZA-919_samza.patch
>
>
> Although the Samza RunLoop is single-threaded, there are other threads used in important areas. e.g. BrokerProxy. It's useful to log the thread name to help reason about how the threads are interacting. 
> Also, the time stamps are currently logged with second granularity which can make it hard to identify events that happen on sub-second time scale. 
> This ticket is to update the log4j configurations in the samza and hello-samza repositories to include millisecond timestamp granularity and threadname.



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