Metrics: histograms for aggregate share and collection job size in reports and batch aggregations
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- backend, observability
Research direction
Review the existing aggregation job size instrumentation referenced in issue #2730 and trace how reports, collection jobs, aggregate shares, and batch aggregations are represented. Define metrics for collection-job and aggregate-share sizes in reports and batch aggregations, plus reports per batch aggregation; done means these metrics are emitted and expose the requested sizes and counts.
Written by the indexing model from the issue text.
Description
For a given task, collection job requests and responses and aggregate share requests and responses always have the same size, so we can't tell based on HTTP message size metrics whether handling an aggregate share requires summing up 10 batch aggregations DB rows or 10,000. We should emit a metric for the size of collection jobs and aggregate shares, both in number of reports and number of batch aggregations.
While we're instrumenting stuff, it would also be nice to get insight into how many reports there are per batch aggregation.
Previously, we did this for aggregation job size: https://github.com/divviup/janus/issues/2730
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
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.
More from divviup/janus
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100