Article XIV · Operator Station
What’s up,
right now.
Live readout as of . The page isn’t cached; a refresh always pings every instrument fresh.
STATION · WATCH
UNIT 47-N · S/N 0001DEGRADED· STATION REPORT
Degraded performance
At least one component is responding more slowly than the SLO target. Service is still available.
Components · Primary Instruments
API · STATUS
UNIT 47-N · S/N 0B88STATUSDEGRADED
READOUTresponding in 1089 ms
LATENCY1089 ms
WORKER QUEUE · STATUS
UNIT 47-N · S/N 103DSTATUSONLINE
REPORTresponding in 0 ms
LATENCY0 ms
SIGNAL COMPUTE · STATUS
UNIT 47-N · S/N 608FSTATUSONLINE
REPORTlast signal triggered no data yet
BRIEF SEND · STATUS
UNIT 47-N · S/N DBC4STATUSONLINE
REPORTlast brief delivered no data yet
MVIEW REFRESH · STATUS
UNIT 47-N · S/N 2095STATUSONLINE
REPORTmv_org_active_signals refreshed no data yet
Performance + Freshness · Extended Readouts
Fleet-wide SLOs reported per V5 §14. All numbers are aggregated across every workspace — no per-customer data is shown here.
BRIEF DELIVERY ON-TIME (24H) · STATUS
UNIT 47-N · S/N 913ASTATUSONLINE
REPORTno briefs scheduled in last 24h
SIGNAL COMPUTE FRESHNESS · STATUS
UNIT 47-N · S/N 845CSTATUSONLINE
REPORTno signals computed yet
INTEGRATION INGEST LAG · STATUS
UNIT 47-N · S/N 6D5CSTATUSONLINE
REPORTno activity events ingested yet
Sub-channels
- slackno data yetONLINE
- githubno data yetONLINE
- google_calendarno data yetONLINE
CLAUDE ERROR RATE (24H) · STATUS
UNIT 47-N · S/N 4729STATUSONLINE
REPORTerror tracking not enabled (ai_outputs.error_class missing)
QUEUE DEPTH (WORKER TICK LAG) · STATUS
UNIT 47-N · S/N D4F7STATUSONLINE
REPORTqueue depth telemetry unavailable
Memo · To Operator
Reporting an issue
Seeing something here that doesn’t match what you’re experiencing? Email yash@sonarwork.com with what you’re seeing + your workspace name. We respond within 1 business hour during incidents.
Last updated
Machine-readable health: /api/health · 200 = DB + Redis up, 503 otherwise. Historical uptime graphs on the roadmap.
Filed28 JUN 26