Alerting subscribers of failed report uploads or aggregations (including rate limit excession)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
Report uploads or aggregations could fail due to misconfiguration of clients or a peer DAP aggregator. For example, uploads could fail because the wrong HPKE configuration was used, or report aggregations could fail if clients were configured with the wrong number of histogram buckets. These are scenarios that have to be remedied by someone external to Divvi Up.
To help subscribers resolve this kind of problem, Divvi Up's control and data planes should detect high rates of upload or aggregation failure and somehow inform the subscriber of it. For instance, emailing the subscriber and putting a warning banner on the Divvi Up website when the subscriber logs in or when they navigate to a particular task's page.
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
The issue names no files, tests, or entry points. Start by mapping the control and data planes, then determine how failed uploads or aggregations are measured and how subscribers should be notified; done means high failure rates reliably trigger an actionable subscriber warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100