Repository navigation
Publish a run's logs, whole-run node metrics and specs to the dashboard - #462
Merged
Merged
Conversation
radiken
marked this pull request as ready for review
November 17, 2026 12:07
radiken
force-pushed
the
alan/dashboard-fetch
branch
from
November 17, 2026 12:09
b1ba943 to
d85e33c
Compare
radiken
force-pushed
the
alan/dashboard-coverage
branch
from
November 17, 2026 12:09
78bc597 to
99fc708
Compare
AlbertoSoutullo
approved these changes
Nov 17, 2026
… dashboard Besides the 13 stable-window metrics, each run stores every metric the nodes' own scrape job reported on any statefulset's first pod, plus container CPU, throttling, memory and network and the pods' host and start time, per pod at 30 s over the whole run. nim-libp2p runs also store their sends and deliveries (the dashboard parses only that tracer), checked against the run's summary CSVs; metadata adds the events and deployed specs. A metric that every pod reports with the same labels and value for the whole run is recorded in metadata.unchanged with the rule, not stored; fetch.run_dataset returns it as one row per pod. A publish deletes only an experiment it created and could not check. On a 409 the stored run is checked and an error raised if it is short, but it is never deleted: it may still be processing, or hold data VM no longer has. The loader reads datasets one at a time instead of all at once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
radiken
force-pushed
the
alan/dashboard-coverage
branch
from
November 18, 2026 01:20
99fc708 to
3220ef0
Compare
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.
Each run now also stores the nodes' metrics from every statefulset, container CPU, memory and network, and the pods' host and start time, per pod at 30 s over the whole run. It also stores the run's sends and deliveries (nim-libp2p, checked against the run's CSVs) and its events and deployed specs. Metrics that every pod reports with the same labels and value for the whole run go into the metadata instead (
UNCHANGED_RULE). A 409 now checks the stored run and raises if it's short, but never deletes it, since it may still be processing or hold data VM no longer has; a publish only deletes what it created. About 300 MB as JSON for a 1k-node run.