Repository navigation
Report Core process metrics and node host history - #108
Merged
Merged
Conversation
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
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.
Core metrics previously exposed only Go heap memory, and node dialogs had no host CPU or retained host history. This adds process CPU/RSS and cgroup limits to the existing Core metrics response, plus an administrator-only node detail read with real heartbeat observations and 1h/6h/24h history.
Both reuse existing sampling and storage: Core's 30-second ring and the Runtime sweep with PostgreSQL seven-day retention. Missing measurements, initial CPU samples and offline buckets remain null. The node list and public Agents API schemas, enrollment/capacity policy and frontend pages are unchanged. API contracts, generated admin OpenAPI and SQLC, and architecture documentation are updated.
Validation:
7192e3f: full Linuxmake checkpassed on mx1, including database tests, 610 client tests, 332 Web unit tests, 12 browser tests and executor checks. The private test copy used Chromium; the existing optional MiniMax packaged-tools test remained skipped.The first full check failed on macOS metadata accidentally copied into its private test tree; rerunning the entire gate from a clean Git archive passed. Seven-day aging uses database fixtures; no seven-day wall-clock observation or model execution is claimed. Latest main #101/#106 was checked for overlap; neither changes this batch's backend files. Existing demonstration services were not upgraded.