feat(dashboard): [#304] implement per-metric detail pages and endpoint - #307
Merged
ApusBerliozi merged 2 commits intoAug 5, 2026
Merged
Conversation
ApusBerliozi
self-requested a review
August 5, 2026 06:16
ApusBerliozi
approved these changes
Aug 5, 2026
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.
Fixes: #304
Changes
GET /session/<project_name>/<session_id>/metric/<metric_name>route (session_metric_detail) tofenn/dashboard/app.py, reusingscanner.get_session()— no scanner or type changes required.<metric>points matchmetric_namefor that session (there's no metric registry independent of recorded data, so an unknown name and a known-but-empty name both 404 — matches the acceptance criteria's "unknown metric name" wording).fenn/dashboard/templates/session_metric_detail.html, extendingbase.htmlwith breadcrumbOverview › <project> › <session> › <metric_name>, mirroringsession.html's#session-metrics-dataJSON-blob pattern (scoped to the single metric's points instead of the full list) and its.chart-card/chart-svgmarkup so existing chart-rendering JS can pick it up unmodified..chart-cardheaders insession.html(train_loss,val_loss,acc), pointing aturl_for('session_metric_detail', ...).Notes
scanner.pyortypes.py—get_session()already returns the fullmetricslist; filtering bymetric_namehappens in the route.