Skip to content

metrics: decide dashboard coverage for Kafka producer response rate #5879

Description

@3AceShowHand

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.

Metadata

Metadata

Assignees

Labels

component/kafkaTiCDC kafka sinkcomponent/metrics-loggingMetrics and logging component.priority/P3The issue has P3 priority. Assigned to backlog.type/enhancementThe issue or PR belongs to an enhancement.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions