bin log not captured in kafka debezium

[Tejendra Shrestha]

Hello, i have aws msk and msk connect configured successfully, however, bin log from rds mysql is not being captured in consumer. I have a doubt if it is actually produced to kafka. 

I can see multiple internal topics created as part of setup. My configuration as below : 

connector.class=io.debezium.connector.mysql.MySqlConnector
tasks.max=1
database.hostname=xxxxxxxxxxxx.rds.amazonaws.com
database.port=3306
database.user=xxxxx
database.password=xxxxxxxxxxxx
database.server.id=123456
database.server.name =rds1
database.include.list=health_company1
table.include.list=health_company1.test_table
column.include.list=health_company1.test_table.policy_id,health_company1.test_table.ssn
topic.prefix=test
schema.history.internal.kafka.topic=health_company1.test_table
schema.history.internal.kafka.bootstrap.servers=b-2-public.qacluster.8xnxeo.c6.kafka.us-east-2.amazonaws.com:9198,b-1-public.qacluster.8xnxeo.c6.kafka.us-east-2.amazonaws.com:9198
schema.history.internal.consumer.security.protocol=SASL_SSL
schema.history.internal.consumer.sasl.mechanism=AWS_MSK_IAM
schema.history.internal.consumer.sasl.jaas.config=software.amazon.msk.auth.iam.IAMLoginModulerequired;
schema.history.internal.consumer.sasl.client.callback.handler.class=software.amazon.msk.auth.iam.IAMClientCallbackHandler
schema.history.internal.producer.security.protocol=SASL_SSL
schema.history.internal.producer.sasl.mechanism=AWS_MSK_IAM
schema.history.internal.producer.sasl.jaas.config=software.amazon.msk.auth.iam.IAMLoginModulerequired;
schema.history.internal.producer.sasl.client.callback.handler.class=software.amazon.msk.auth.iam.IAMClientCallbackHandler
include.schema.changes=true

Debezium version : 2.4

I do not see any topics being created corresponding to table change in mysql side. could you please guide me through this. ? 

[jiri.p...@gmail.com]

Hi,

could you please share the full connector log?

J.