Stream fleet visibility
Watch every CDC stream under a project with health, lag, heartbeat age, rows applied, and last-hour activity.
MySQL CDC Monitoring
See whether MySQL CDC is healthy, caught up, and still moving changes.
Cupcake DRCP turns CDC into an operator view: stream fleet, heartbeat freshness, lag, rows applied, workload mix, source load, binlog state, and recent technical events.
Why It Matters
Turn database movement into an operating workflow.
Binlog and fallback awareness
Track source position and window mode so teams know whether change capture is using binlog replay or a row-window sweep.
Guardrails for drift
Surface conditions such as disabled foreign-key checks so teams know when compare and repair should be scheduled.
Product Workflows
Related Cupcake DRCP screens.
Checklist
Binlog CDC vs primary-key sweep CDC tradeoffs
Step 1
Use binlog CDC when near-real-time replay and source position tracking are the priority.
Step 2
Use a primary-key sweep when binlog access is unavailable or when a fallback validation pass is needed.
Step 3
Watch heartbeat age, rows applied, and lag together so quiet traffic is not confused with a stalled stream.
Step 4
Schedule compare and repair after CDC catch-up when foreign-key ordering or fallback sweeps could create temporary drift.
Community Discovery
Useful MySQL operations topics to keep exploring.
FAQs
Quick answers.
What should operators watch first?
Lag, heartbeat age, rows applied, last error, and source position are the first signals to inspect.
Can technical CDC events still be reviewed?
Yes. Cupcake keeps the operator summary readable while preserving technical event history for deeper troubleshooting.