-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
Feature request or enhancement
This feature already exist in MySQL, Postgres, and Oracle connectors. This request is for SQL Server.
Which use case/requirement will be addressed by the proposed feature?
We have a separate table where we want to track if the engine is really running and track the latency from source to target. This table contains a timestamp column and we want to use the heartbeat query to insert/update GETDATE() value in there (or run any user provided SQL).
In the past we have experience engine issues where the engine status is in a running state (based on JMX metrics), but it was not doing anything. Having heartbeat action query will help us identify if the engine is doing any activity rather than solely rely on the metrics provided by Debezium. This basically provides us another option to validate if engine is running/active.
- links to
-
RHEA-2024:139598 Red Hat build of Debezium 2.5.4 release