Jobs per NodePool metric
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Hi, we are trying to scale a node pool based on the allocated resources from that node_pool. The problem is that if the pool has 0 nodes, we can't use that for the 0 -> 1 scaling action, so we need something like jobs running/pending in node_pool.
Maybe it makes sense to simple update the job_summary metric to include the node_pool.
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 job-summary metrics reference and trace how that metric is implemented in Nomad. Determine how running or pending jobs can be grouped by node_pool, including pools with zero nodes, then add coverage and update the metrics documentation. Done means node-pool job counts are available for scaling decisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100