Console Usage view with utilisation and waiting charts
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 52/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- playwright, typescript
- Área
- documentation, frontend, testing
Línea de trabajo
Start with ui/src/views/index.tsx, ui/src/views/usage.tsx, and ui/src/views/usage-model.ts, then read the referenced architecture and design rules. Run the model, resource, chart, and Playwright tests named in the issue. Done means the Usage view matches the specified figures and charts, refreshes on the stated schedule, works at 360 px in both colour schemes, passes the axe check, and is documented in docs/CONSOLE.md.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Part of #329.
Scope
After this PR, the console has a Usage view: a window picker (last hour, day, week), the figures as stat cards and tables, and two charts, utilisation and waiting over time, that update without a reload as the window moves. It follows the design guide, works at 360 px and in both colour schemes.
Technical spec
Modules touched
ui/src/views/index.tsx— aUsageentry inVIEWS, path/usage.ui/src/views/usage.tsxandui/src/views/usage-model.ts(pure, unit-tested) — the view and its model. The model turns oneusage.getanswer into the stat-card rows, the table rows and the two chart series; the view renders them withStatCards,Panel, the shared table fromui/src/table.tsx, and a chart built onui/src/charts.tsx.ui/src/charts.tsx— the chart takes a bucketed series with any width and formats the axis bybucketMs, whichMinuteChartassumes to be a minute today; the accessible table beside it does the same.- Data: a variant of
useLiveResourceinui/src/live/live-context.tsxthat refetches/v1/stats?since=<window>every 15 seconds while on screen and never more often; an event marks the resource stale for the next tick, not a fetch of its own; the window is in the URL's search (?window=1h|24h|7d) throughuseSearch, default24h. partialrenders as a note above the figures withcoversFrom.- On a worker the per-worker table has one row, itself; on a gateway one per worker. The per-requester table shows the label beside the id.
e2e/console/usage.spec.ts— Playwright, on the fake driver.docs/CONSOLE.md— the view.docs/internal/DESIGN.mdif a token or rule is added.
Contract and event changes
- None. The view reads
GET /v1/statsand the existing event stream.
Rules in play
architecture.mdrule 1: the model is pure and the view reads one route.testing.mdrule 1: each Playwright test title is a claim about what is on screen.docs/internal/DESIGN.md: charts have their numbers in an accessible table, animation off, colour by class; tables stack under 768 px; no horizontal scroll at 360 px; contrast AA in both schemes.
Tests
- the usage model turns an answer into stat cards for requests, grants by source, wait p95, held p50, peak utilisation and rejections
- the usage model turns the series into a utilisation chart series of slots used over max and a waiting chart series of requests waiting per bucket
- the usage model formats the window and the partial note from
coversFrom - the Usage resource refetches on the 15-second tick and not on the one-second tick, and an event does not start a fetch before the next tick
- the chart formats the axis by bucket width for one-minute, fifteen-minute and one-hour buckets
- (console) the Usage tab shows the figures for the last 24 hours by default and the picker switches to the last hour and the last week
- (console) after a lease is granted while the view is open, the request count rises within 15 seconds without a reload
- (console) the utilisation and waiting charts render with their accessible tables, and every number in a chart appears as text
- (console) at 360 px the view has no horizontal scroll and the tables stack
- (console) the view passes the axe check in light and dark schemes
- (console) on a gateway with two workers, the per-worker table has two rows; on a single host it has one
Done when
- On the fake driver, after a scripted run, the Usage view shows the figures and both charts for the chosen window, matching
simlock stats --jsonfor that window. - Taking a lease while the view is open raises the counts within 15 seconds without a reload.
- The view works at 360 px with no horizontal scroll, in light and dark schemes, and passes the console lane's axe check.
- On a gateway the per-worker table has one row per worker; on a worker it has one row.
docs/CONSOLE.mddescribes the view and its window picker.
Out of scope
- Explicit start and end dates in the console; the three fixed windows only. The CLI and the route cover arbitrary windows.
- Any chart beyond utilisation and waiting.
Depends on
- #348
Approval
- Approved for delivery
Written by an agent.
- Lenguaje dominante
- TypeScript
- Estrellas
- 15
- Forks
- 1
- Merge medio
- 8 h 23 min
- PR fusionados (30 d)
- 136
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de callstackincubator/simlock
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
callstackincubator/simlock#424 ·
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
callstackincubator/simlock#422 ·
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
callstackincubator/simlock#420 ·
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
callstackincubator/simlock#350 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Flaky e2e: gateway-fleet reads a worker's capacity before the worker has left startingPosiblemente ocupada @V3RON la tomó hace 2 días. Abiertobug:ready flaky-test
Dificultad 4/5 1-2 días Aptitud para principiantes 48/100
callstackincubator/simlock#414 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de callstackincubator/simlock
Issues similares
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
core
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
vectorize-io/hindsight#5457 ·
Los mantenedores suelen responder en 1 día
-
beginner friendly community contributions-welcome good first issue hacktoberfest help wanted testing up-for-grabs
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
lukilabs/beautiful-mermaid#160 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
rescript-lang/rescript-lang.org#1420 ·
Los mantenedores suelen responder en 2 días