Observability and management for Janus job queues
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
https://github.com/divviup/janus/issues/2781 discusses giving Janus interfaces for managing aggregation and collection job queues. Once these are wired up in the aggregator API, divviup-api could do stuff with them like:
- Admin consoles allowing DU ops to manage queues
- Expose job backlog metrics to subscribers
While operators can technically do this by directly tickling the Janus aggregator API, it's much nicer to have this exposed in divviup-api, where we can gate access on Auth0 users.
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 with the linked Janus issue about interfaces for managing aggregation and collection job queues, then review how the aggregator API is exposed through divviup-api. Done would include a defined approach for queue management and backlog metrics, with access gated on Auth0 users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authentication, backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100