Use Case Description
MySQL to ClickHouse replication is critical for data consistency.
Currently, there is no built-in alerting when replication fails, stops, or becomes unhealthy, which can lead to undetected data gaps and delayed issue response.
Proposed Solution
Provide a way to detect and alert on replication failures, such as:
Replication process stopped or crashed
Errors reading MySQL binlogs or writing to ClickHouse
Replication lag exceeding a configurable threshold
Connection failures to MySQL or ClickHouse
Alerting could be implemented via logs, exposed metrics (e.g. Prometheus), webhook support, or clear health/status indicators.
Alternatives Considered
External scripts and log parsing, which are indirect and increase operational complexity.
Additional Context
Native alerting or health signals would greatly improve observability and production reliability.
Use Case Description
MySQL to ClickHouse replication is critical for data consistency.
Currently, there is no built-in alerting when replication fails, stops, or becomes unhealthy, which can lead to undetected data gaps and delayed issue response.
Proposed Solution
Provide a way to detect and alert on replication failures, such as:
Replication process stopped or crashed
Errors reading MySQL binlogs or writing to ClickHouse
Replication lag exceeding a configurable threshold
Connection failures to MySQL or ClickHouse
Alerting could be implemented via logs, exposed metrics (e.g. Prometheus), webhook support, or clear health/status indicators.
Alternatives Considered
External scripts and log parsing, which are indirect and increase operational complexity.
Additional Context
Native alerting or health signals would greatly improve observability and production reliability.