Observability of "Couldn't update tasks" errors
Open
Nobody has claimed this yet.
observability
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
We need some sort of metrics that we can alert on when the aggregation job creator encounters errors fetching tasks. We had a submarine error here, which resulted in it spawning no async tasks and doing no work.
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 by locating the aggregation job creator and the path where fetching tasks produces "Couldn't update tasks" errors. Review existing metrics and determine how to expose these failures so an alert can detect when no asynchronous tasks are spawned; done means the error condition is measurable and alertable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100