Watch your Postgres → ClickHouse CDC
Point chmonitor at your PeerDB API and every mirror gets live status, rows-synced trends, lag triage and slot health — read-only, proxied, no agent.
Every mirror on one screen
Status tiles for the whole fleet — running, snapshotting, paused, failed — with rows-synced trends and the worst-lag strip pointing at the mirror that needs you first.
- Live status per mirror
- Rows-synced trends over time
- Worst-lag triage strip
Drill into any pipeline
Batch history, partition sync progress, peer info and pipeline phase per mirror — plus aggregated logs and alerts filterable by severity.
- Batch history and partition progress
- Replication-slot health across peers
- Logs and alerts, filterable by severity
More of PeerDB replication in action
Everything in the box
Fleet status
All mirrors and their phases, live.
Sync trends
Rows synced over time per mirror.
Lag triage
Worst lag surfaced first.
Slot health
Replication slots across peers.
Logs & alerts
Aggregated, severity-filterable.
No agent
Read-only proxy to the PeerDB API.
Common questions
What do I need to connect?
Just your PeerDB API endpoint and credentials — chmonitor proxies read-only requests, no agent on either side.
Can chmonitor pause or edit mirrors?
No. The integration is strictly read-only monitoring.
Does this replace PeerDB’s own UI?
It complements it: chmonitor puts CDC health next to your ClickHouse and Postgres monitoring in one dashboard.
More chmonitor features
Start monitoring — advisor and alerts built in
Open the hosted dashboard and connect a cluster, or self-host with Docker, Kubernetes, or from source. Self-hosting is always free.