Repository navigation
Conversation
A console screen with tabs that go one level deeper each. Summary has four gauges (handled without a person, closed today, time to decide, AI spend against its cap), what needs attention, the day at a glance and the fleet settings, read-only; its main column and the settings scroll on their own. Throughput has the day by hour and work by workflow. Paused and stuck shows what waits, by age. Decisions, Sources and memory, and System are placeholders that say what they will show. The day chart draws cases running against the cap and alerts in beside cases closed as two panels on one hour axis, each on its own scale, with one crosshair tooltip across both. GET /api/pulse/summary, /throughput and /work validate their answers against PulseSummary, PulseThroughput and PulseWork in core/monitor/models.py. The reads are not implemented: each route answers 501 and its tab shows its error state, except in demo mode, where it serves the seeded sample in core/monitor/fixtures.py. Taken from krmayankb/vigil PR #7 (fleet/console-monitor). Co-authored-by: krmayankb <krmayankb@gmail.com> Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: gray <egboluche.g@gmail.com>
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.
Stacked on #2273 (Fleet Wall); review that first. This PR's diff is Pulse only.
What
A Pulse console screen (nav: Overview → Pulse → Fleet Wall). It shows the fleet summarized, every number against its limit, in tabs that each go one level deeper:
Day chart. Cases running against the cap is one panel; alerts in beside cases closed is another. They share the hour axis, each has its own labelled scale, and one crosshair tooltip spans both (it also works with arrow keys). Charts draw at their rendered width, so text keeps its size.
The API is a contract, not an implementation
GET /api/pulse/summary,/throughputand/workare defined byPulseSummary,PulseThroughputandPulseWorkincore/monitor/models.py:The reads (
core/monitor/pulse.py) are not implemented:The docstrings list the sources and TODOs: hourly bucketing in SQL, and no counting dead runs as running.
Tests
monitor.test.tsx: Summary gauges, levels, chart and attention links; the oldest waiting case opens.main.Origin
Taken from @krmayankb's krmayankb/vigil PR #7 (
fleet/console-monitor), credited as co-author.