Ops dashboard
The sample Bastion screen: status bar, edge-region latency map, services table, deploy timeline, a resolved incident, a log tail, and an ops-agent suggestion with Approve and Dismiss. Figures match the approved layout. They are not a live cluster.
Change the region, pause the tail, refresh metrics, open an incident or the deploy list (Escape closes it), then approve or dismiss the suggestion. Approving sets worker to 4/4 on this page only.
SAMPLEFictitious telemetry. Approve, dismiss, refresh and region changes stay on this page.
ALL SYSTEMS NOMINAL
| Service | Status | CPU | Memory | Replicas |
|---|---|---|---|---|
| api | RUNNING | 18% | 41% | 3/3 |
| worker | RUNNING * | 62% | 67% | 2/3 |
| db | RUNNING | 24% | 58% | 2/2 |
| cache | RUNNING | 11% | 32% | 2/2 |
INC-2025-0417-03 RESOLVED
High latency on ap-southeast-1
Root cause: Elevated packet loss on upstream provider.
Resolved by rerouting traffic via alternate peering.
Detected Apr 17 09:12 · Resolved Apr 17 09:47
- [INFO]Ops agent health check passed
- [INFO]All regions nominal
- [INFO]Worker queue depth: 128
- [WARN]High CPU on worker (62%)
- [INFO]Scaling recommendation generated
- [INFO]Suggested action: scale worker to 4 replicas
- [INFO]Awaiting operator confirmation…
Ops Agent sugiere escalar worker a 4 réplicas
Razones:
- CPU utilization sostenido > 60% en los últimos 10m
- Cola de trabajo creciendo (depth: 128)
Confianza del agente: 82%
What is on the screen
| Region | Role |
|---|---|
| Status bar | Wordmark, ALL SYSTEMS NOMINAL, region select, uptime and sparkline |
| Latency map | Dotted field, eight sample cities, legend for <20ms, 20–50ms, and >50ms |
| Services | Status, CPU, memory, replicas. Worker starts at 62% CPU and 2/3 replicas |
| Deploys | Four hashes. d2e4f6a is marked Review, not color alone |
| Incident | INC-2025-0417-03, resolved sample |
| Log tail | bastion-ops-agent, with pause |
| Ops agent | Spanish recommendation, 82% confidence, Approve and Dismiss |
Responsive
At desktop widths the panels sit in two columns. Around a tablet width, and whenever the frame is under 860px, they stack. The service table scrolls inside its panel on a narrow phone. Status controls wrap instead of forcing the page sideways.