feat(ui): redesign log viewer with structured request rows#65
Merged
Conversation
Turn the uniform "Request completed" TRACE wall into a scannable stream: pull HTTP method/path/status/latency inline as aligned monospace columns, add a log-scaled latency lane and a severity rail so slow or failed lines surface out of the trace flood, fold consecutive identical lines into a single row with a repeat counter, and add a path/status/message filter. Row expansion now shows a key-value field table with copy and raw-JSON instead of a bare JSON dump.
An unrecognised severity string was cast straight to LevelKey, missing LEVEL_STYLES and mis-rendering as INFO — a high-priority line could lose its label and rail. Only trust severity when it's a known label; otherwise fall through to the numeric pino level.
When a record carries a custom severity string with no numeric level, show its own uppercased label with a lit rail (and index it for filtering) rather than collapsing it to INFO — so a high-priority line can't pass as normal.
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.
Why
The log viewer rendered every line identically —
time · TRACE · "Request completed" · ⌄— with all the useful detail (method, path, status, latency) hidden behind the chevron. A flood of identical TRACE request lines drowned the one line that mattered, and nothing was scannable.What changed (logs viewer only)
http.*/durationMsfields are pulled inline as aligned monospace columns: verb-colored method, path, status (colored by 2xx/3xx/4xx/5xx), and latency. The redundant "Request completed" message is dropped.×Ncounter (avg/max latency shown on expand). Toggleable via "Collapse repeats".Files
apps/ui/app/pages/logs.vue— rewrote the view; streaming/reconnect logic preservedapps/ui/app/components/LogRow.vue— new; row + detail panelapps/ui/app/utils/logFormat.ts— new; level/method/status/latency/grouping helpersapps/ui/app/assets/css/main.css— one added line:--font-mono(JetBrains Mono, self-hosted by @nuxt/fonts, system-mono fallback)apps/ui/.env.example— ridealong: documents the UI BFF env varsNo other page is touched.
font-monois only used by the log stream; every other view stays on Inter.Verification
nuxt typecheckandeslintboth clean.Greptile Summary
This PR redesigns the UI log viewer to make request logs easier to scan.
Confidence Score: 5/5
This looks safe to merge.
Reviews (3): Last reviewed commit: "fix(ui): surface unrecognised log severi..." | Re-trigger Greptile