The control room
The control room is the browser dashboard at /admin. It turns calls and texts into incidents people can act on. The header on every page shows the WebSocket link, the gateway mode and when the Kaaka number was last seen.
Pages
| Page | What it shows |
|---|---|
| live | Open and acknowledged incidents, newest activity first. Each card shows the caller, calls and alerts, the latest location, the nearest responders with distance and ETA, and [timeline →] and [resolve] buttons. Below it the incident map with trails, nearest-responder lines and a [hotspots] overlay, then the activity log. |
| history | Resolved incidents. Search by digits of the number, filter by outcome (resolved by responder / closed by caller) and by date, [load more] 20 at a time, [download csv] with the same filters. |
| incident | One caller's full timeline: calls with the reply result, help SMS text, alerts with coordinates, location shares, dispatches, ACKs and the resolution. A map of the caller's trail. [resolve] while still active. Open it from any number or [timeline →]. |
| analytics | One range filter (24h / 7d / 30d / all). KPI tiles: incidents, open now, median and p90 time to ACK, median time to close, % located, % replies sent, closed by caller. Charts: contacts per day by channel, contacts by hour, outcomes, a responder leaderboard. Each chart has a [table] view. |
| responders | The responder registry (add, availability, remove, [pick on map]) with each responder's dispatches and ACKs. |
| system | The raw latest alert, live sensor tiles, telephony details and the test triggers. |
The address keeps the page (for example /admin#history), so reload and back work. Counts show next to live, history and responders.
Incident status
- open: needs attention, highlighted.
- acknowledged: a responder replied ACK.
- resolved: closed by a responder's RESOLVE, the caller's SAFE (shown with a green "safe" badge and "closed by caller"), or the [resolve] button. A later call, help SMS or alert reopens it.
Incidents group everything by the caller's number (its last 10 digits). History is kept in the data directory and reloaded when the server restarts.
The map
OpenStreetMap tiles through Leaflet, so it needs internet. Offline, the panel says the map is unavailable and everything else works. Each incident's latest location is a pin; a caller who keeps sharing leaves a trail. A dashed line runs from the nearest available responder to each open incident, labelled with distance and ETA.
Notifications
On a Mac the server posts a system notification for a new or reopened incident, an acknowledgement, a resolution, and when the Kaaka number goes silent or comes back. Turn them off with --no-notify or KAAKA_NOTIFY=0.
Export
[download csv] on the history page, or GET /api/incidents.csv with the same filters. Columns: number, status, first and last seen, counts of calls, help SMS and alerts, latest coordinates, who acknowledged and resolved and when, and the note.
Kaaka 1.0.0 · Edit this page · In immediate danger, call 112.