Layout and Controls

The Spider Sense UI is a single browser page: a sidebar that lists the pages, beside a top bar of controls that every page obeys.

Overview: the stat tiles
Figure 1. The Overview, with the stat tiles, the Findings panel, the throughput chart, and the response summary

How the UI is built

The UI lives in spider-sense-server/src/main/resources/public and is served as Spider Silk static files. It has no build step: plain HTML, one CSS file, and ES modules. The time-series charts and the scatter are drawn with uPlot (MIT), vendored under public/assets/vendor/. The service map is hand-drawn SVG. All data comes from the HTTP API, and the page never renders server-side.

Look and feel

The name

"Spider Sense" is the sibling of "Spider Silk": Silk is the web a spider builds, and Sense is what the spider feels through it, the tingle when something on the web moves. In the UI the tingle is the sidebar’s signal for a slow request, a slow query or an error: the logo’s sensing arcs pulse once and the tingles entry shows a count, on whatever page is open.

The logo is notes/logo.svg in the repository, also served as /assets/logo.svg. It keeps the Spider Silk family motif, a spider, a web and the tingle, in a 200×200 viewBox with a transparent background. Four closed, scalloped web rings and eight continuous radial strands in #8a93a6 extend to the hub behind the larger eight-legged spider in #e2603f. The web stays complete in every quadrant, with the same geometry as Spider Silk’s. The strands use a 2.2-unit stroke and the outer ring a 3-unit stroke. Three evenly spaced coral sensing arcs overlay the intact north-east quarter. The anomaly dot sits at (159.4, 40.6), where the north-east radial meets the outer ring. It is outside the animated group, so it stays attached to the web during a pulse.

The sidebar repeats this geometry inline, with the spider in currentColor, the web in --text-muted, and the sensing arcs and the dot in --accent. Its .sense-arcs group carries the event-driven pulse of the tingle badge, centred on the spider’s head at (100, 96), and respects a reduced-motion preference. A monochrome variant, logo-mono.svg, uses currentColor throughout, and defaults to black when embedded as an image. The 32×32 favicon draws the same complete web, spider and three sensing arcs on a rounded dark tile, with a light spider for contrast.

The README’s logo and the served full-colour SVGs are kept identical. The inline sidebar logo and the monochrome variant change together with them.

Palette

The palette uses the same tokens as the Spider Silk badges, extended for a dark UI.

Token Dark Light Use

--bg

#171a21

#f6f7f9

The page

--bg-panel

#1f232c

#ffffff

Cards and tables

--bg-raised

#2b303b

#eef0f4

Hovers, inputs, the sidebar

--line

#343a47

#dde1e8

Borders and grid lines

--text

#e6e9ef

#1f232c

Text

--text-muted

#949db0

#5f6878

Secondary text, the strand grey

--accent

#e2603f

#d1532f

The tingle: primary actions, the active nav item, slow markers

--accent-strong

#c4452a

#c4452a

The accent behind white text: the primary button, the tingle badge

--accent-text

#ea8e76

#ab3c25

The accent set as text or as an icon: a link’s hover, the active page and tab, a pressed toggle, the slow-call count, a chart’s p95 axis, a mark’s name

--ok

#5ec27f

#2e9e57

Healthy

--warn

#f0b64b

#c98c14

Slow

--err

#e5484d

#c9363b

Errors

--ok-text, --warn-text, --err-text

--ok, --warn, #f6827f

#1b723e, #845d00, #b02d2c

The three status colours set as text or as an icon rather than as a fill

--info-text

#72b6ea

#246297

The INFO severity and the GET method label, whose tint and border stay --series-5

--silk

#8a93a6

#8a93a6

Strands, neutral chart lines

--spider

#5a3a22

#5a3a22

Rarely: the logo only

Dark is the default. prefers-color-scheme: light switches to the light palette, and so does a toggle in the top bar, or in the sidebar’s foot below 720 px, which is persisted in localStorage. A browser that refuses the storage starts on the default and keeps a toggle until the page is reloaded. Each palette sets the CSS color-scheme too, so the parts the browser draws itself, a select’s list, the scrollbars and a number field’s spinners, follow the toggle rather than the system. A scrollbar is thin on everything that scrolls, the window included, with a transparent track. Its thumb is --text-muted at 75%, the least that keeps 3:1 on --bg, --bg-panel and --bg-raised of both palettes. The accent colour marks the primary actions, the active page in the sidebar, and what is slow.

Text is set in the system UI font stack. Ids, statements and stack traces are set in a monospace stack.

Services and span categories take their series colours from a fixed list of eight derived from the palette: accent, silk, ok, warn, then four muted hues. A service is assigned its colour in first-seen order, so it looks the same in every chart. A toggle of the theme recolours everything at once: the canvas charts rebuild in the new palette, and the colours set on the page’s elements, a chip’s dot, a legend’s swatch, a sparkline, a waterfall bar, are the tokens themselves (var(--series-3)), which the browser repaints.

Response-time buckets and Apdex

The response-time buckets are the four of /api/status.thresholds.responseBucketsMs plus errors (Status). Each has one fixed colour, used wherever a histogram or a load chart appears.

Bucket Token Label

1

--bucket-1 = --ok

≤125 ms

2

--bucket-2 = --series-8 (teal)

≤500 ms

3

--bucket-3 = --warn

≤2 s

4

--bucket-4 = --accent

>2 s

Errors

--err

error

The labels are built from the bounds, so the ones above are those of the default thresholds.

Apdex is shown with one decimal less than the API carries, as in 0.93. It is coloured --err below 0.7, --warn below 0.85, and plain otherwise. The colour follows the value as shown, so an API value of 0.849, shown as 0.85, is plain, as 0.85 is. The tile’s caption says apdex, and its title says the T it was computed with.

Tone of the copy

The copy is short and factual, with no exclamation marks. An empty state explains how to send data, with the OTLP endpoint from /api/status in a copyable snippet, rather than saying "No data".

Layout

┌──────────────┬──────────────────────────────────────────────────────────────┐
│ ◉ Spider     │  ‹page title› [⚑ Mark] [Service ▾] [Last 15 min ▾] [● Live] [☀] │
│   Sense      ├──────────────────────────────────────────────────────────────┤
│              │                                                              │
│ Overview     │                                                              │
│ Findings     │                                                              │
│ Compare      │                        page content                          │
│ Map          │                                                              │
│ Services     │                                                              │
│ Scatter      │                                                              │
│ Traces       │                                                              │
│ Queries      │                                                              │
│ Errors       │                                                              │
│ Logs         │                                                              │
│ JVM          │                                                              │
│ Metrics      │                                                              │
│              │                                                              │
│ ──────────   │                                                              │
│ ⚡ tingles    │                                                              │
│ standalone   │                                                              │
│ :4000  v0.1  │                                                              │
└──────────────┴──────────────────────────────────────────────────────────────┘

The sidebar lists the pages: Overview, Findings, Compare, Map, Services, Scatter, Traces, Queries, Errors, Logs, JVM, and Metrics. It is 220 px wide, collapses to icons below 1100 px, and becomes a drawer behind a hamburger button below 720 px. Every entry carries its name as a title and an aria-label, so a collapsed icon still says where it goes. So does the foot’s tingles entry, whose aria-label also gives the count its badge shows, as in Tingles, 3 new. Collapsed, the foot’s How to send data and Clear data stay reachable as two icon buttons, a tray and a bin, with the same titles. The selected page fills the rest of the window, under the top bar.

The top bar

The top bar carries the page title on the left, and on the right the Mark button, the service filter, the time range, the editor setting, the Live toggle, and the theme toggle. The title takes what the controls leave and cuts the rest with an ellipsis. A select holds at most 200 px and cuts a long service or mark name the same way, and the selects narrow before anything leaves the bar. An open drawer leaves the bar as little as a small window does, so beside one, up to 1460 px wide, the top bar drops the readout and the editor select, as below 720 px.

Mark

The button shows the word Mark beside its flag from 1100 px up, as Live shows its word, and the flag alone below that or up to 1240 px beside a drawer. It opens a small dialog with a name, an optional note, and OK. The name matches [A-Za-z0-9._-]{1,64}: letters, digits, dots, underscores and hyphens, up to 64 characters. It is prefilled with before when no mark in the window is named before, and with after otherwise. When the service filter names one service, the mark records that service as its service. OK sends POST /api/marks and shows a toast naming the mark. The server refuses a name a selector reads as something else, such as 5m, now or start, and the dialog stays open with the reason. A mark made here is the same row the CLI’s mark <name> writes, so findings --since=<name> and compare read it. Marks covers what a mark is and how the agent’s side reads it.

Service filter

Selects all services, or one. It applies to every page that takes a service. A service= in the URL that names no service Spider Sense has seen stays selected, as <name> (not seen), so the filter that empties the pages is in sight and can be set back to all services.

A service, endpoint, query or error page belongs to one service, so the select shows that service and the page’s URL names none. A service= in such a URL is dropped, not obeyed. An endpoint, query or error page learns its service from its answer, and until then the select keeps the service the link carried. The page’s links carry its service, so the next page keeps what the select shows. Choosing another service leaves the page, since the page cannot show it: a service or endpoint page opens that service’s page, and a query or error page opens the Queries or Errors page filtered by it. Choosing all services opens the list the page belongs to: the Services page from a service or endpoint page, and the Queries or Errors page from the others. A trace crosses services, so a trace page keeps the filter as any list does.

Time range

The presets 5m, 15m, 1h, 6h and all, then Since start, and under it the marks a person or an agent made, newest first, each name once. all sets from to /api/status.oldest.span, the oldest span in storage. The shell re-reads /api/status on every route change and every Live refresh, and under all the page waits for it, so the window grows as data arrives, and after a Clear data, an import or another process’s writes. With no span in storage, oldest.span is 0 and all is the last 15 minutes.

Since start sets from to the mark --since=start reads, and Since before the one --since=before reads (Time selectors). start is the newest automatic start mark, of the service filter’s service when one is chosen, and a mark’s name is the newest mark of that name, the service’s own first. to is now, and Live moves it. The marks are re-read as the status is, and under a mark the page waits for them, so a restart moves Since start at the next refresh. A mark that no longer exists, or a service with no start, stays selected as <name> (not seen), last 15 min, as the service filter’s does, and the page shows the last 15 minutes, which is what the select says. A recording offers its one preset and no mark, and the Compare page only the comparisons it holds (The recording).

Editor

A select of Open code in IntelliJ IDEA, the default, or Open code in VS Code: what a code frame link opens, on the Findings page and the error page (Code frames). The choice is remembered in localStorage and applied at once to every link on the page. Every access to the storage is wrapped in try, so a browser that refuses storage keeps the default.

Live

On by default: the page re-fetches every 5 seconds, and the to of the window moves with the clock. The state comes from the hash when it says, as live=1 or live=0, else from the choice remembered in localStorage, as the theme’s is and with the same guard, else on. A press writes both, and every internal link carries what the hash says. While the tab is hidden no refresh runs, and when it shows again one runs at once, so a Live left on in a background tab sends no request. The server’s stats event (Events) drives a "spans/s" readout beside the toggle. With Live off the readout goes, and as of 10:12:03 sits beside the time range in --text-muted: the moment the data on screen was asked for, updated by every load. It is a button that reads the page’s data again, in full, on every page. Every tingle event reaches the badge on the sidebar’s tingles entry (The tingle badge). It folds into the Overview feed without a refetch, unless the top bar names another service.

Time-series charts

Every time-series chart takes the top bar’s window as its x-axis, however little of it the data covers, so an instant falls at the same place on every chart of a page. A bucket is aligned to the epoch, so the first one starts at or before the window, and the axis reaches back to it. A chart with no point yet still draws the axis. A sampled series, such as the heap of a process that started five minutes ago, leaves the part of the window before its first point empty. The tooltip reads the nearest point within one step of the series, or 16 px at the least. Over an empty stretch it stays hidden.

The time-series charts of a page share a cursor. The pointer on one draws the cursor line and the points at that instant on all of them, so the values of one instant can be compared across the charts. The tooltip stays on the chart under the pointer.

Marks on charts

Every time-series chart draws the marks that fall inside its window as a vertical dashed line the full height of the plot, with the name as a small label at the top. Marks fewer than 6 px apart draw as one line at the first of them, so services that start together do not merge into a band. One line stands for marks across 24 px at the most, so it stays beside what it names. Its label gives the names in time order, counted where one repeats, as start × 5 or start × 4, before. The automatic start marks are in --text-muted, and every other mark is in --accent, with its name in --accent-text. A line that holds both is in --accent. A label is drawn over the lines on a halo of --bg-panel, so a line beside it does not cross it. A label that would overlap the one before it is left out. With the pointer on a line, the tooltip lists its marks with their services and times, the first six and a count of the rest. A mark that names a service is drawn only when the service filter is off or is that service. The marks come from GET /api/marks?limit=50, which the shell fetches on every route change and every Live refresh and keeps in the shared state. Under a range that names a mark it asks for 500, the most the server gives, so a quiet service’s start is still found behind other services' restarts. A page therefore never fetches them itself, and every chart draws them from the shared state.

The tingle badge

When a tingle event arrives, the accent-coloured sensing arcs of the logo in the sidebar pulse once, a 600 ms CSS animation. The arcs pulse once for an event and stay still between events. The badge on the sidebar’s tingles entry counts rows of the feed rather than occurrences: one service, kind and title counts once since the last reset, however often it repeats. The pulse respects a reduced-motion preference.

The entry opens the Overview scrolled to the Tingles feed, with the focus on the feed, from any page and from the Overview itself. It links to #/?focus=tingles and carries the top bar’s query, as every internal link does (URLs). On the Overview itself the page stays and reads its window again, because what the badge counts may have come after the page loaded. Once the feed is in view the focus key leaves the hash, so a reload does not scroll the page again. The badge goes back to zero when the feed has been shown, not on the click, so a page that fails to load leaves the count as it was.

Dialogs

A dialog closes on Esc, on its close button, and on a click on the backdrop that also began on the backdrop. A drag that starts in one of its fields and ends outside it, as when selecting the text, leaves it open.

How to send data

Has three tabs: -javaagent, environment variables, and curl. Each tab is a copyable block carrying the actual endpoint from /api/status, and its Copy button shows without a hover. The -javaagent and curl lines single-quote an endpoint a shell would read as a pattern, such as 'http://[::1]:4000', so zsh takes them as they are. The environment variables keep it bare, since a shell reads no pattern in an assignment and an IDE’s field would keep the quotes. The -javaagent lines name /api/status.jar, the jar the server was started from, or spider-sense.jar when the server does not know it. A bare -javaagent gives the application a Spider Sense of its own, embedded on :4000, so it leads only where the page comes from such a one: in agent mode on http://127.0.0.1:4000. In standalone mode, or on any other endpoint, the line with -Dspidersense.collector=<endpoint>, which sends here, comes first, and the bare line follows under # or start a Spider Sense of its own, embedded in the app. The empty states show the same three blocks, with their Copy buttons always shown too.

Clear data

Asks for confirmation, saying what DELETE /api/data deletes and what it keeps, then sends it. A 204 reloads the page and shows the toast Data cleared. Any other answer, or no answer, shows Data not cleared: and the error in the toast instead, and leaves the page as it was.

Keyboard

Key What it does

/

Focuses the query bar

Esc

Closes a drawer, or clears the scatter selection

L

Toggles Live

[ and ]

Step the time range through its presets; from a mark, go to the nearest preset that way, the longest shorter than the window or the shortest longer than it

M

Opens the Mark dialog

?

Opens a small dialog that lists these keys

The controls name their keys in their titles: the Mark button Mark this moment (M), the time range Time range ([ and ] step it), and the Live toggle Live updates (L).

The keys act only outside a text field and while no dialog is open. An open dialog keeps the keyboard to itself, and Esc closes it. The Mark dialog opens once at a time.

URLs

Routing is hash-based: #/, #/services/spring-orders, #/traces/<id>, and so on. The service filter and the time range live in the hash query, as in #/traces?service=x&range=1h, and a range that names a mark is range=start or range=mark:<name>, as in range=mark:before. So do Live, as live=1 or live=0, and the Requests | Load choice of the throughput charts, as chart=requests or chart=load (Overview). Every internal link carries these four, so a choice made on one page holds on the next. The sidebar’s entries, the logo and the tingles entry are rewritten on every change of the hash, so they carry them too. Every link a page has already built is rewritten too, such as the Overview’s All findings or the links of an open finding’s evidence, and leads to the service, range and Live the top bar shows when it is followed. A path parameter is percent-encoded in the hash and decoded once, so a service named 50% off is #/services/50%25%20off, and an encoded / stays part of its name. A URL can therefore be shared as it is, and opens on the same view. A hash the page did not set itself, from a link, Back or Forward, or an edited URL, opens its view the same way, on the page already open too, so the page never keeps a filter, a sort or a metric the URL no longer names. A change made on the page, in the top bar or in the page’s own controls, keeps the page and refreshes what it shows. The one exception is the service filter on a page of one service, which leaves that page (The top bar).

Behaviour and quality

Live refresh

Every list re-renders in place when Live refreshes it, without losing the scroll position or the selection. A table row keeps every cell whose content did not change, so a focused link or selected text in it stays. A cell that changed is replaced, and the focus it held moves to the same place in the new cell. A row that changes place, as a finding does when its rank moves, keeps the focus it holds. A select’s options, such as the Compare page’s marks or the Traces page’s endpoints, are rebuilt only when they changed, since a browser closes an open list whose options change. A page paints only the answer to the newest of its requests: an older range, filter or page that answers last is dropped, so a slow all never overwrites the 5m asked after it, and a Load more still pending when the filter changes adds nothing to the new list. A Live tick that comes while a load of the page has not answered yet leaves that load alone, so a slow answer, such as the findings over a long window, is not asked for again behind itself. Meanwhile the page keeps showing what it has, and the Live button carries a small spinning ring. A change of filter, range or page is no tick, and always loads at once. A load nobody will paint is aborted: the one a newer load of the same page supersedes, and the one still out when the page is left. The server finishes the statement it is on regardless, within the 30 seconds of How it is read, and a read it stops at that bound reaches the page as a Request failed box with its Try again, never as a panel that keeps loading.

When the server is not answering

A request that gets no answer at all, because the Spider Sense the page came from has stopped, shows an error box headed Not answering. It says Spider Sense at <origin> is not answering. Start it again and reload, or try again., with the page’s own origin, and carries a Try again button. The sidebar foot’s mode reads not answering until the status answers again. The first answer after a request that got none, such as the one Try again sends once the server is back, makes the shell read /api/status and /api/services again, so the foot and the service filter come back with the server. A refusal, an answer with an error status, keeps the Request failed heading and the server’s sentence.

Numbers and times

Durations carry one decimal below 100 ms and none above, and are given in seconds (s) above 10 s. A chart’s tooltip follows that rule, each duration carrying its own unit. A finding’s title and why do not follow it: they are the text rendering’s own sentences and keep its numbers, one decimal at any size, as in p95 3,403.3 ms. They are the bytes the findings command prints and Copy as Markdown copies, so the page and the CLI print the same title and why for a finding. A grouped message in them keeps its ? masks, as in request timed out after ?ms, and the sample’s exception chain on the error page holds the values. The records on the Logs page hold the values of a log-error, which has no error page. The ticks of an axis labelled ms stay in milliseconds, with thousands separators, so one axis never mixes two units. Counts carry thousands separators, rates two decimals, and percentages one. A count with its noun takes the singular for one alone, as in 1 span, 1 call or 1 request, and the plural for any other count. A value of no particular unit, a gauge, a histogram’s mean or a sum’s rate, is whole from 100 and keeps three significant digits below it, in a tooltip and on an axis alike. A count axis only ever shows whole numbers, with uPlot incrs of 1, 2, 5, 10 and so on, so a series that stays at 0 or 1 does not print the same tick three times. An axis is a count axis when it is no duration, percentage or load and every value on it is a whole number; a metric of fractions keeps its own scale. A value axis is as wide as its widest tick, and 52 px at the least, so a count in the billions keeps its leading digits and stays clear of the axis label. A value axis starts at 0, or 15% under the lowest value when one is below 0, so a gauge that goes negative stays in the plot. Times read as HH:mm:ss within today, and MMM d HH:mm:ss otherwise. The length of a window reads in its two largest units, as in 7 s, 1 min 8 s or 2 h 5 min. A chart’s time axis reads the clock, with the day, MMM d, under its first tick when that tick is not today and under the first tick of each later day, and a chart’s tooltip and the Scatter’s selection follow the rule above. Its ticks stand at least a second apart, so a window that starts at a mark a moment ago never prints one time twice. A feed gives the relative time, "12 s ago", a table the absolute one, and a tooltip both.

Narrow screens

The whole UI works at 360 px wide: a table scrolls horizontally inside its panel, the charts shrink, and the drawer becomes a full-screen sheet. The page itself never scrolls sideways. The Findings table is the exception that does not scroll: below 720 px its rows read as the Overview’s finding rows (Findings). Below 720 px the sidebar sits behind a menu button at the top left, and the top bar and the recording’s note start to the right of it; the top bar drops the editor select, the theme toggle moves to the sidebar’s foot, and the other selects narrow before anything leaves the page. The title takes what the controls leave, whatever its length. With Live off and below 520 px, as of gives the time alone. Below 420 px the waterfall’s name column narrows, so the timeline still fits.

Every table fits its panel at 1280 px and wider, under a 15 px page scrollbar too, so every column is on screen without scrolling. Its columns have fixed widths, and the wide column takes the rest: a statement, an error message, a trace’s root or an endpoint is cut with an ellipsis, the whole of it in the title, and a log body wraps. No other cell widens the table: its text and its chips are cut the same way. Every such cut stops before a surrogate pair it would split, such as an emoji, as the store’s cuts do. Below 200 px for the wide column the table scrolls instead, or below 160 px in Top errors and Slowest calls. A trace table holds the service chips in that column too, so it scrolls below 320 px, except in the narrower panels of Slowest calls and of the error page’s Recent traces, which stay at 160 px and 200 px. The endpoint, query and error pages each name their one service in the header, so a table there has no Service column. A trace row on them gives chips only for the other services in the trace. A table that scrolls sideways fades at the edge there is more of, and the fade goes once that edge is reached. A table that fits its panel keeps its header in view on a long page, stuck under the top bar. A table that scrolls sideways, in a narrower window or beside an open drawer, does the same with a copy of its header, which shows once the header reaches the top bar. The copy has the header’s columns and scrolls sideways with the table, without a scrollbar of its own, and its sort buttons sort as the header’s do. A swipe or a wheel that starts on the copy moves the table, as one on the rows moves the copy, and the two reach the far right end together. The copy is aria-hidden and out of the tab order, so a screen reader and the keyboard reach the header itself. The two swap as the panel’s width changes. A row the keyboard reaches scrolls clear of the top bar and of a stuck header.

Accessibility

Every icon-only control has an aria-label. Colour is never the only carrier of meaning: an error also gets a bolt, and something slow also gets a ring or a turtle. Text reaches WCAG AA’s 4.5:1 on every background of both palettes: a status colour set as text takes its -text token, the accent set as text takes --accent-text, the INFO severity and the GET method label take --info-text, and white text sits on --accent-strong. The two tokens of the accent and the INFO blue are set apart from the colours they stand for because those miss 4.5:1 as text: --accent reaches 3.76:1 on the dark --bg-raised and 3.69:1 on the light one, the light --accent-strong 4.35:1 there and 3.76:1 on --accent-soft, and the light --series-5 3.72:1 on --bg-raised. The fills, the borders and the chart series keep the colours themselves. A status chip tints its background with its status colour: 14% for a severity, 12% for the sidebar’s storage chip, a regressed finding and a Compare verdict. The status -text tokens keep 4.5:1 on those tints over every background, including the --bg-raised of the sidebar and of a hovered row. Their ratios are these, on the three backgrounds and on the tint each sits on, --accent-soft for a pressed toggle, a chip or the active page, --series-5 at 14% for the INFO severity, and the status colour at 12% or 14% for the status chips:

Text On --bg On --bg-panel On --bg-raised On its tint, at least

--accent-text, dark

7.15:1

6.46:1

5.43:1

4.63:1

--accent-text, light

5.75:1

6.17:1

5.41:1

4.67:1

--info-text, dark

7.95:1

7.19:1

6.04:1

4.76:1

--info-text, light

5.99:1

6.42:1

5.63:1

4.79:1

--ok-text, dark

7.88:1

7.12:1

5.98:1

4.77:1

--ok-text, light

5.56:1

5.96:1

5.22:1

4.63:1

--warn-text, dark

9.53:1

8.61:1

7.24:1

5.38:1

--warn-text, light

5.52:1

5.92:1

5.19:1

4.60:1

--err-text, dark

6.98:1

6.31:1

5.30:1

4.69:1

--err-text, light

6.01:1

6.45:1

5.65:1

4.63:1

Dimmed text is set in --text-muted, never in a colour at a reduced opacity. An opacity under 1 fades only what holds no text: a hidden series' swatch, an acknowledged finding’s dots, and the boxes, icons, curves and bands the Map leaves out of a highlight. A chart writes the text on its canvas in the text tokens too: an axis drawn in a colour, such as the --accent p95 axis, writes its values and its label in that colour’s text token, or in --text-muted when the colour has none.

A clickable table row takes the focus, and Enter or Space on the row does what a click does. A row that opens a detail row holds a disclosure button at the start of its first cell, on Findings, on Logs and in a trace’s logs. The button states aria-expanded, and aria-controls while the detail row exists, since ARIA defines neither on a row outside a treegrid. The button is that row’s stop in the tab order, so the keyboard meets one stop per row, the one that says whether it is open. The row itself takes the focus only from a click. Enter on a link or a button inside the row belongs to that control: the link opens, and the row does not act. A sort keeps its table: the focus stays on the header that was pressed, the table stays where it was scrolled sideways, and only the header’s marks and the order of the rows change. A press on the stuck copy of a header (Narrow screens) leaves the focus on the header itself, so the next Tab goes on from there. The Queries page sorts through a select and asks the server: the select keeps the focus and the table stays until the answer, and after a failed answer the select still sorts. A sort the hash names when a page opens takes no focus, since nobody pressed a header. Below 720 px the Findings table is no longer displayed as a table, so its header is hidden from sight only, and every element states its role (table, rowgroup, row, columnheader, cell), so a screen reader still names the column of a cell such as ongoing. A drawer takes the focus when it opens, and closing it gives the focus back to the row that opened it, unless the person has moved the focus elsewhere in the meantime. A toast is a polite live region that is in the page from the start, so a screen reader reads the first toast as it reads the later ones.

No external requests

The UI makes no external request at all: the fonts are the system’s, uPlot is vendored, and the logo is inline. The one exception is the recording, which reads every answer from DoltHub’s SQL API (The recording).

Size

The UI a browser loads is under 600 KB uncompressed, excluding uPlot. assets/js/dev/ does not count: it ships in the jar, but a page loads it only for the mock and the recording.

The mock

?mock=1 loads assets/js/dev/mock.js, which answers every endpoint of the HTTP API the UI asks for, so every page can be developed without a server. That includes /api/map, /api/scatter, /api/findings, /api/findings/{id}, /api/marks (GET and POST), /api/compare, /api/source, ErrorGroup.series, /api/status.codeFrames and jar, the histograms, and the connection pools. DELETE /api/data deletes the mock’s traces, logs, tingles, notes and marks, and keeps each service’s newest start mark, as the server does. The endpoints the UI never asks for, /api/check, POST /api/sql and POST /api/import, are not mocked. Under the mock every source frame resolves, under a made-up project directory. The mock has no text renderer: a format=text request answers a stand-in naming the path, with the JSON in a fenced block.

The recording

assets/js/dev/replay.js answers the UI from a recording, the DoltHub database of the published demo (The demo without installing anything). It is loaded when <html data-dolthub="owner/database@ref"> or ?dolthub=… names the database, and it answers every GET /api/… from that database through DoltHub’s SQL API, from the browser. A read that fails on the network or with a 5xx is tried three times; when the first read, the manifest, still fails, the page says the recording could not be read from DoltHub, and why.

Some answers are queried from the tables of Storage and shaped as the HTTP API says:

  • the traces, /api/traces, with service, endpointId, minMs, maxMs, status, by, q, before, beforeId and limit applied as the API applies them;

  • one trace, /api/traces/{id}: its spans in the waterfall’s order, each with the server’s summary line, and its logs, a trace of more than 1,000 spans being cut at DoltHub’s row limit;

  • the logs, with service, severity, q, traceId, before and beforeId;

  • the marks;

  • the acknowledgements, the ack rows that are not resolutions.

Everything else is read from the answer table by path and query, without from and to. A request whose filters were not recorded falls back to the nearest recorded answer, dropping one filter at a time, and logs the substitution, as a warning when the filter dropped is service, since that means a capture is missing. A comparison’s before, after and until are its windows, not filters, so none of them is ever dropped. A format=text answer is replied as the text it was captured as.

The recording freezes Date.now() at the end of the window. It makes the default top-bar range the length of the recording: the 15m preset becomes "The recording (5 min)", so every chart covers the recorded minutes and none before them. That preset is the only one offered, since every other range would answer the same aggregates. It answers POST and DELETE with 405, and /api/source with 404, since the files are not in the recording. It replaces EventSource with one that never emits, and hides Live and Clear data, which would do nothing. Live stays off: L does nothing, a live= in the URL is dropped from it, no as of shows, and the ? dialog leaves L out, so the recording never polls DoltHub for answers that cannot change. It puts one line above the top bar saying when the recording was made and what it holds (the four example applications and the load generator), where to start (Findings, or the agent demos of Claude Code and Codex over the same recording), and a link to the database. It is the one page of the UI that makes external requests, since it reads every answer from DoltHub’s SQL API.

The Compare page offers only the comparisons the recording holds. capture asks by mark name, never with until, and keeps no refusal, so a pair of marks has an answer only when the server answered it. Before lists the marks that open a pair the recording holds, After the marks held with the chosen Before, and Until is not shown. A start mark that shares its name with others, a reversed pair and a mark against itself are therefore not offered. A link can still name them, and the page keeps what of it has an answer. An until goes from the hash, an After with no answer gives way to the newest After held with that Before, and a Before with none to the default pair.

scripts/demo-site.mjs assemble copies public/ into one directory with data-dolthub set on index.html. That directory is the static demo the manual publishes at /demo.