Metric, UI and cli for memory_hard_limit
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Since `memory_hard_limit` is implemented via https://github.com/hashicorp/nomad/pull/8087 it would be great if we could get metric for it (like `nomad_client_allocs_memory_total` or `nomad_client_allocs_memory_hard_limit`).
In our case an over-limiting (soft+hard limits) is used widely, so `memory_hard_limit` value in the metrics/alerts is more important than `memory_allocated`.
Another improvement would be displaying `memory_hard_limit` information in the UI and nomad-cli (e.g. `nomad alloc status ID` ).
Thanks!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing memory_hard_limit implementation referenced through Nomad PR 8087 and compare it with the nomad_client_allocs_memory_total metric. Then trace how allocation data is exposed to the UI and to nomad alloc status ID. Done means memory_hard_limit is represented consistently in metrics, the UI, and the CLI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, frontend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100