Support changefeed traffic metering and reporting
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
Is your feature request related to a problem?
TiCDC needs to report traffic metering results per changefeed through Metering SDK. The reporting infrastructure should be independent of how traffic is measured and persisted.
Describe the feature you would like
Provide an opt-in metering destination and a coordinator-owned traffic reporter that accepts typed results, uploads batches with bounded retries, and returns initialization and upload errors. Metering credentials must be redacted from configuration logs and the configuration API.
The complete feature also needs sink integration, durable metering state, periodic submission, and an agreed consumption contract. Those can be developed separately from the reporting infrastructure.
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
No file, test, or entry point is named. Start by defining the coordinator-owned boundary between traffic measurement, persistence, and reporting, then clarify the typed results, opt-in destination, bounded retries, and error behavior. Done means batches upload through the Metering SDK while initialization and upload errors are returned and credentials are redacted from logs and the configuration API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100