client: expose allocated CPU per task #6784
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #4280 and #5526
Modeled after #5492
Using the currently exposed metrics there is no way to calibrate per-task CPU allocation based on recent usage. This would be helpful, for example, to identify tasks which are greatly over-allocated in terms of CPU.
This PR adds
client.allocs.<job>.<group>.<alloc>.<task>.cpu.allocated
as a gauge in CPU ticks.