NADI OPS

Control Plane Operations

Separated frontend for server health, queue drift, and fast recovery actions.

Operator Runbook

  1. Set API URL, admin email, and admin secret, then refresh.
  2. Watch KPI cards for stale heartbeats and failed-permanent ops (counts show assigned peers/devices, not live handshakes).
  3. Use server filter for focused scope during incidents.
  4. Use requeue only for stale leased ops; it retries stuck operations.

Connection

Server Action Bar ?

Create/update servers and disable old nodes
No recent server action.

Upsert Server

Server State

Disable for drain/decommission, enable for recovery after maintenance.

Connections Trend ?

Active peers

Handshakes Trend ?

All nodes in one graph (or filtered node)

Server Status ?

Not loaded
healthy degraded action required

Tip: on small screens, scroll table horizontally to see Runtime and Actions columns.

Server Location Active Assigned Connections Assigned Devices Live Handshakes Assignment Gap Heartbeat Capacity Tier Runtime Load Runtime Bandwidth Status Actions

Device Inventory ?

Not loaded
Device Platform Server Connections Last Issued

Recovery Actions ?

Requeue expired leased operations for selected scope.

Event Log

Ready.

Recent Admin Actions ?

Not loaded
Time Admin Email Action Target