You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Damian Guy (JIRA)" <ji...@apache.org> on 2017/09/18 08:54:00 UTC

[jira] [Resolved] (KAFKA-5754) Refactor Streams to use LogContext

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

Damian Guy resolved KAFKA-5754.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Issue resolved by pull request 3727
[https://github.com/apache/kafka/pull/3727]

> Refactor Streams to use LogContext
> ----------------------------------
>
>                 Key: KAFKA-5754
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5754
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Jason Gustafson
>            Assignee: Umesh Chaudhary
>              Labels: newbie
>             Fix For: 1.0.0
>
>
> We added a {{LogContext}} object which automatically adds a log prefix to every message written by loggers constructed from it (much like the Logging mixin available in the server code). We use this in the consumer to ensure that messages always contain the consumer group and client ids, which is very helpful when multiple consumers are run on the same instance. Kafka Streams requires similar contextual logging by including the prefix manually in each log message. It would be better to take advantage of the new {{LogContext}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)