Runbooks
Operational runbooks for Kafka Connect and Debezium
Procedures for Kafka Connect and the Debezium MySQL connectors on zwingproddb.
Connector runbooks
A. Connector task failed
Change data has stopped. Check the task, confirm the database is back, and restart one connector at a time.
B. Events missing while the connector was running
A change never arrived, and the connector task did not fail. Separate delay, a missing table, a consumer problem, and real loss.
Who to call
| Area | Owner |
|---|---|
| GIP connector and consumers | Mukesh |
| Reporting and item master connectors, reporting service | Chetan |
| Kafka Connect, AKS, Azure MySQL | Chandramani |
| Outbound connector | To be confirmed |