Debezium Server
Debezium Server is a smaller way to run change data capture. Varqeni reads the engine's own health in place of Kafka Connect's status.
AvailabilityAvailable to everyone with early access to Varqeni.
How it works
- What it reads: the engine's health endpoint, its pods and log, the replication slot, the engine's heartbeat and the topic it writes to, read-only. A pipeline without a schema registry is not judged on one.
- What it names: the engine down or failing, and a source with nothing to capture, which is not a fault. The other checks a connector on Kafka Connect gets, such as a slot holding too much WAL, run too, but are not yet trialled on this engine.
- What it does: recommends only. Varqeni runs no fix on Debezium Server; restart or fix it where it runs.
- In the lab it named the cause in 30 of 30 blind trials on a Debezium Server reading the same source as a Kafka Connect pipeline.
What it can and cannot do
Can
- Watch Debezium Server like a connector: engine health, slot, heartbeat and topic, and name the cause when it breaks.
Cannot
- Restart or change Debezium Server: it recommends only on this engine.
Related articles
- Read the live pipelineThe Overview opens on your pipeline: the diagram first, then a panel with each part's key number, its recent history and the rate moving between parts.
- What is plannedIntegrations on the way, none of which are available today.
Still stuck? Contact support or email info@fortisdatagroup.com.