anchor.diff:  
   == Logging concepts
   
  -Each log message produced by the application will be sent to a specific _logger_. Every logger has a name (e.g., `io.debezium.connector.mysql`), and the names form a _hierarchy_ of loggers: the logger named `io.debezium.connector.mysql` has a parent logger named `io.debezium.connector`, which has a parent logger named `io.debezium`, all the way to the _root logger_ at the very top of this hierarchy.
  +Each log message produced by the application will be sent to a specific _logger_. Every logger has a name such as `io.debezium.connector.mysql`, and the names form a _hierarchy_ of loggers. For example, the logger named `io.debezium.connector.mysql` has a parent logger named `io.debezium.connector`, which has a parent logger named `io.debezium`, all the way to the _root logger_ at the very top of this hierarchy.
   
   Every log message produced by the application will also have a specific log _level_:
   
  
positive.code: 
  The containers also use the `LOG_LEVEL` environment variable to set the log level for the root logger. So, all you have to do is set this environment variable to one of the log levels (e.g., `-e LOG_LEVEL=DEBUG`), and all of the code within the container will start using that log level. For example:
  
  If you need more control, create a new image that is based on ours, except in your Dockerfile copy your own `log4j.properties` file into the image:
  
  [source]
  .Dockerfile
  ----
  ...
  COPY log4j.properties $KAFKA_HOME/config/log4j.properties
  
negative.code: 
  This means that you can easily control all of the log messages for a specific class or for all of the classes within a package. For example, to turn on debug logging for the MySQL connector (and the database history implementation used by the connector) might be as simple as adding the following line(s) to your `log4j.properties` file:
  
  [listing,indent=0,options="nowrap"]
  ----
  ...
  log4j.logger.io.debezium.connector.mysql=DEBUG, stdout <1>
  