-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide telemetry about allocated / available resources #2191
Comments
If i understand correctly, you can calculate it for CPU, Memory and disk space easily by using the following two: |
@stew Are you asking for each client to report its allocated and available resources? You could then aggregate for a cluster wide view |
@dadgar that would be ideal, yeah. Does it make sense? |
@OferE yeah, and you see exactly the stats I'm looking for when you look at the output of |
@stew Yep I was just clarifying to make sure we add the right thing |
@stew Do these stats not work for you: https://github.com/hashicorp/nomad/blob/master/client/client.go#L2147. They don't take into consideration reserved however |
Adding reserved stats would be cool yes! |
@dadgar yeah, I do have multiple ways of getting at that stat that work, I guess the reserved stuff is what I'm really after. I want to build stats to help me figure out when I'm close to expecting allocations to get blocked due to a lack of resources. |
This is what I'm looking for to prevent cluster reservation saturation, maybe AutoScale cluster when less then threshold resources left |
here is more telemetry per task #2330 |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
0.5.2
I'm wanting to collect telemetry about how much of my cluster resources have already been allocated, and I don't see any current telemetry which allows me to figure out stuff like "how much memory does my cluster have unallocated" "how much cpu do I have unallocated" "what is the most amount of unallocated memory on any client currently", which is telemetry I feel like I need in order to know when I should be scaling my cluster up.
The text was updated successfully, but these errors were encountered: