metrics: decide dashboard coverage for Kafka producer response rate
@3AceShowHand is already working on this.
Since Aug 5, 2026.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
What to build
Decide how TiCDC should expose and consume ticdc_sink_kafka_producer_response_rate. The metric is currently defined, registered, periodically updated from Sarama broker metrics, and cleaned up when the collector stops, but it is not referenced by the Classic, NextGen, or with-keyspace-name Grafana dashboards.
If response rate provides independent operational value for diagnosing Kafka broker communication, add consistent dashboard coverage. If it does not provide useful information beyond the existing request-rate and in-flight-request signals, remove the unused metric and its collection cost.
Acceptance criteria
- The operational value of Kafka producer response rate is explicitly decided and documented in the change.
- If retained, Classic, NextGen, and with-keyspace-name dashboards expose the metric with filters and grouping consistent with the other broker-level Kafka producer panels.
- If removed, its definition, registration, collector update, cleanup, and generated dashboard references are absent.
- Relevant Kafka metrics tests and dashboard generation checks pass.
Blocked by
None - can start immediately.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.