kafka sink write bytes / s metrics should be calculated based on the raw entry
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
Now it's calculated based on the encoded kafka message. Not matched to the ticdc input bytes / s, this is not expected.
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.
Research direction
Start at the Kafka sink's write-bytes-per-second metric calculation and trace whether it uses the encoded Kafka message or the raw entry corresponding to TiCDC input. Done means the metric is based on raw-entry bytes and matches TiCDC input bytes/s rather than encoded-message size.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- observability, stream-processing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100