Per-capability/arch/feature worker load metrics + by-URL upstream merge (#417) - #490
Merged
Conversation
…by-URL upstream metrics (#417)
…ences, add X-Cache headers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #417.
Per-capability / architecture / feature load: the "Load by capability" radar divided each worker's total in-flight jobs by capacity, so eval/fetch/build always read the same %. New
GET /board/workers/loadaggregates real in-flight jobs from the scheduler's job tracker (which alone knows each job's kind, architecture, and required features) against the summed slot capacity of the workers that can serve each dimension; the Workers page now shows three radars (capability, architecture, feature) so an operator can tell whether the fleet is eval-, build-, or architecture-bound.By-URL upstream metrics:
upstream_metricis re-keyed on the upstream URL (migrationm20260705_000000, with historicalmetric_rollupre-scope + merge), so the same URL registered under several caches/orgs contributes to one series; the cache-latency chart is also un-boxed to match every other graph.