server/workmgr: Track Total Job Runtime
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 238
- PR merge metrics
- No merged PRs in 30d
Description
As an admin, I want the system to keep track of total runtime of a job so that we can potentially take action (stop the job) if it's not providing any value (no cracked passwords)
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 server/workmgr component and reading how jobs are started, monitored, and stopped. Determine where total runtime belongs and how an administrator would observe or use it. Done means a job's total runtime is tracked consistently and the behavior is covered by the relevant existing tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100