Be able to know the percentage of resources used
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Hello,
We want to be able to know if we need to add a new nomad client to handle our tasks or if we have too many nomad client for our load. For that, it could be useful to know how our clients are used (could be related with https://github.com/hashicorp/nomad/issues/2872). Today, we're able to know how our client is used via the `Resource Utilization` graph on each client, but instead of displaying the hardware limit, displaying the nomad's locked resources could be a good metric to estimate our needs.
Thanks
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the client Resource Utilization graph and the related issue #2872. Define how Nomad-locked resources should be measured against client capacity, then update the utilization view to expose the percentage needed to assess client capacity; verify the displayed metric against representative client workloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100