-
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
Emit per-task allocated resources telemetry #4241
Comments
@multanii just moved it to another branch. |
@burdandrei Thanks, I just saw the branch now! As for jippi/hashi-ui, I guess it probably does it by polling Nomad API directly (it's definitely available there). Would be nice to provide them as part of the telemetry process though :) |
Just a bump on this. Because nomad is so strict on memory reservations, it is really crucial to be able to measure a given allocation's usage against its own reservation over time. Measuring this in real time via API is almost pointless because it doesn't account for so many things that can happen while you're not observing the task (nightly process or high load request for example). |
@burdandrei please open up a PR with your branch! I see that #3882 has been merged since your comment :) |
@margueritepd hardly believe that so outdated branch will survive the rebase, but I'll see what's left from it |
Hey there Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this. Thanks! |
Bump |
Doing a little bit of issue cleanup... allocation metrics include task labels. I'm not sure off the top of my head when this was introduced, but see: https://www.nomadproject.io/docs/operations/metrics-reference#allocation-metrics |
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. |
We would like to measure how much resources a task is using compared to how much it reserved in the first place, with 2 specific goals in mind:
AFAIK, there's no allocated resources metrics which are emitted per-tasks. #2327 provides these allocated metrics at the client level. #2330 was supposed to provide these metrics at the tasks level but I guess @burdandrei deleted his branch :) and the code is not available anymore.
The text was updated successfully, but these errors were encountered: