Introduce event seen counter for snapshots [DBZ-5813]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-5813](https://issues.redhat.com/browse/DBZ-5813)
We want to consider adding a snapshot rate metric that is calculated based on the total number of events seen against the snapshot's duration in milliseconds.
We currently only capture the total number of events seen in the common metrics, but this counter is all events, including CREATE, UPDATE, and DELETE. This means that once the connector has transitioned to streaming and if incremental snapshots are started, this metric would be inaccurately calculated.
The {{SnapshotChangeEventSourceMetrics}} should expose a TotalNumberOfSnapshotEventsSeen metric that only tracks the READ events. This snapshot rate should then be calculated based on this event counter and the snapshot duration, which would give an accurate rate calculation for both initial snapshots and for incremental snapshots during the streaming phase.
Contributor guide
Research direction
Start at SnapshotChangeEventSourceMetrics and trace how common event counts and snapshot duration are currently recorded. Verify which events are READ events, then define the snapshot-only counter and rate behavior for both initial and incremental snapshots; done means the metric excludes CREATE, UPDATE, and DELETE events and produces an accurate rate.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100