[jira] [Updated] (KAFKA-3816) Provide more context in Kafka Connect log messages

["Ewen Cheslack-Postava (JIRA)" <ji...@apache.org>]

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

Ewen Cheslack-Postava updated KAFKA-3816:
-----------------------------------------
    Priority: Critical  (was: Major)

> Provide more context in Kafka Connect log messages
> --------------------------------------------------
>
>                 Key: KAFKA-3816
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3816
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.9.0.1
>            Reporter: Randall Hauch
>            Assignee: Ewen Cheslack-Postava
>            Priority: Critical
>
> Currently it is relatively difficult to correlate individual log messages with the various threads and activities that are going on within a Kafka Connect worker, let along a cluster of workers. Log messages should provide more context to make it easier and to allow log scraping tools to coalesce related log messages.
> One simple way to do this is by using _mapped diagnostic contexts_, or MDC. This is supported by the SLF4J API, and by the Logback and Log4J logging frameworks.
> Basically, the framework would be changed so that each thread is configured with one or more MDC parameters using the {{org.slf4j.MDC.put(String,String)}} method in SLF4J. Once that thread is configured, all log messages made using that thread have that context. The logs can then be configured to use those parameters.
> It would be ideal to define a convention for connectors and the Kafka Connect framework. A single set of MDC parameters means that the logging framework can use the specific parameters on its message formats.



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