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: If you're running Debezium connectors in a Kafka Connect process, then Kafka Connect will use the Log4J configuration file (e.g., `config/log4j.properties`) in the Kafka installation. The following are snippets from this file:
  
  [source]
  .log4j.properties
  ----
  log4j.rootLogger=INFO, stdout <1>
  
  
negative.code: * `dbz.connectorName` - The name of the connector as defined in the connector's configuration. For example `products`, `serverA`, etc. All threads associated with a specific connector instance use the same value.
  * `dbz.connectorContext` - A short name for an activity running as a separate thread running within the connector's task. For example, `main`, `binlog`, `snapshot`, etc. In some cases when a thread is allocated for a specific resource (e.g., table or collection), the name of that resource could be used instead. Each thread associated with a connector would use a distinct value.
  
  You can use these properties within the appender's pattern defined in the `log4j.properties` file. For example, the following is a modification of the `stdout` appender's layout to use these MDC properties:
  
  [listing,indent=0,options="nowrap"]
  ----
  ...
  log4j.appender.stdout.layout.ConversionPattern=%d{ISO8601} %-5p  %X{dbz.connectorType}|%X{dbz.connectorName}|%X{dbz.connectorContext}  %m   [%c]%n
  ...
  ----
  
  This will produce messages in the log similar to these:
  
  [listing,indent=0,options="nowrap"]
  ----
  ...
  2017-02-07 20:49:37,692 INFO   MySQL|dbserver1|snapshot  Starting snapshot for jdbc:mysql://mysql:3306/?useInformationSchema=true&nullCatalogMeansCurrent=false&useSSL=false&useUnicode=true&characterEncoding=UTF-8&characterSetResults=UTF-8&zeroDateTimeBehavior=convertToNull with user 'debezium'   [io.debezium.connector.mysql.SnapshotReader]
  