Operational brief · Daily
Operations Daily Standup
Put exceptions, service state, capacity, ownership, and next action into a compact delivered operating report.
- For operations, service owners, and incident or delivery leads
What this standup puts in front of the on-call team
Service health for the last 24 hours, capacity headroom, the two things that need attention and request volume, delivered before the standup starts.
On the page
- Uptime, incidents, latency and error rate
- Per-service latency against SLO
- Capacity headroom by service
- What needs attention, and traffic
Operations · Daily standup
Monday · 09:00 EST
LIVE
Uptime · 24h
99.98%
P0 incidents
0
Avg latency
142ms
Error rate
0.04%
Service health · last 24 hours
| Service | P50 | P99 | Err % | SLO |
|---|---|---|---|---|
| api-gateway | 22ms | 180ms | 0.01% | 99.99 |
| publish-worker | 1.2s | 4.8s | 0.03% | 99.96 |
| render-pool | 820ms | 6.2s | 0.18% | 99.71 |
| scheduler | 14ms | 62ms | 0.00% | 100.0 |
| audit-chain | 8ms | 22ms | 0.00% | 100.0 |
| connector-bus | 340ms | 2.1s | 0.08% | 99.92 |
Capacity · peak use, last 24 hours
- render-pool 86%
- publish-worker 58%
- connector-bus 41%
Needs attention
- render-pool P99 trending up; investigating a cache-miss spike at 03:14 UTC
- connector-bus retry queue depth normal after Friday's deploy
Requests · 24h
00:0012:00now
2.4M requests
Evidence contract
What a production version needs
Operational systems and event streams
Service thresholds and owner assignments
Incidents, blockers, and action status
Recurring workflow
From governed evidence to an approved delivery
- Refresh current service and delivery state.
- Prioritise exceptions against defined thresholds.
- Deliver the brief and carry actions into the next run.
Build the production report behind the plate
Connect your data, keep this design, and set the review and delivery schedule.