anchor.diff:  Looking at the logs you can identify that it actually refers to the entry we just inserted (id 106).
   In addition to that, it refers to missing transaction context data that it cannot find. That is the
   consequence of doing it manually on database level instead of going through the  vegetable service.
  -There is no corresponding data in the transaction-context-data Kafka topic and thus the log enricher cannot
  +There is no corresponding data in the `dbserver1.inventory.transaction_context_data` Kafka topic and thus the log enricher cannot
   correlate and by that merge/enrich them.
   
   == Kogito to the rescue
  
positive.code: </div>
  ++++
  
  or try it yourself by running the https://github.com/debezium/debezium-examples/tree/master/auditlog[audit log example].
  
negative.code: </div>
  ++++
  
  Once the `Use case` and `User name` attributes are provided, the process will create a new transaction context event,
  push it to the Kafka topic and complete itself.
  
  After the missing transaction context data event has been put on the topic the log enricher will resume its operation
  and you will be able to see the following lines in the log:
  
  [source, plain]
  ----
  