...

1. Related local / global variable's values within the function / code block.
    for
   For example, the fetch request string for logging "request handling failures", the current replicas LEO values when advancing the partition HW accordingly, etc.
   
   
2. For exception logging (WARN / ERROR), include the possible cause of the exception, and the handling logic that is going to execute (closing the module, killing the thread, etc).

And here are a few general rules we take for logging format:

1. Each logging entry is usually one-line for the ease of text parsing tools upon trouble shooting, unless it will cause a very long line that may span over multiple screens (for .
   
   For example, the topic-change listener firing log, that may contain hundreds of partitions information).
   

...

1. 
   
2. The logging indent need to be concise and self-distinctive (this is usually also related to client id naming).
   
   
3. Use canonical toString functions of the struct whenever possible.
   
   For example, instead of using "topic [%s, %d]".format(topic, partitionId), use "topic %s".format(TopicAndPartition(topic, partitionId)).

Logging Cleaning Actions

Based on some discussions around these points, we have proposed several actions so far to clean our logging for now, this following list may expand as we discuss along:

...