Hi Dhanya,

Thanks for raising this. This is a helpful callout.

We understand how impactful it can be when CDC is disabled at the source, as it effectively stops replication for the affected tables and can lead to data gaps downstream. Proactive visibility into this state would certainly help teams react more quickly.

Just to confirm, is this specific to SQL Server CDC sources, or are you seeing this need across multiple CDC-enabled connectors?

We’ve heard similar feedback from other customers around improving observability and alerting for source-side issues like this. While I don’t have a timeline to share just yet, this is an area we’re actively discussing internally.

In the meantime, every comment and upvote helps us prioritize this work, so please feel free to add any additional context on how you’d like these alerts to behave (e.g., frequency, severity, notification channels).

We’ll keep you posted as we have updates here.

Best, 
Rean Rodriues, Product Manager Databases