Prometheus metric counting how often leader replays aggregation job continue requests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
One of the PRs related to #994 teaches Janus to detect in VdafOps::handle_aggregate_continue_generic whether an AggregationJobContinueReq received from a DAP leader is a replay of a previous request. To help assess the value of DAP's round skew recovery, we should measure how often this happens.
Contributor guide
No contributing guide indexed for this repository
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 VdafOps::handle_aggregate_continue_generic and review how Janus currently detects replayed AggregationJobContinueReq messages from a DAP leader. Trace the existing metrics instrumentation, then define and expose a Prometheus metric that counts these replay events; done means the counter reports each detected replay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus, rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100