USER GUIDE
Remote edge
Purpose¶
NOC scenarios: sat_down, offline, gpu_hot, intrusion, flood, drone_patrol.
When to use it¶
- Open Remote edge when the job matches this screen
- Prefer the product home / Get started panel if you are unsure where to begin
- Confirm health and auth tokens if probes fail
How to get there¶
- UI path:
/ui/→ Remote edge (or matching nav tab) - Spotlight / in-app links when available
Operate from the console (UX)¶
- Open the relay-edge UI (
/ui/) onhttps://<host>:…(see Admin basics for the default port). - Navigate to Remote edge.
- Complete the on-screen fields / actions for this surface (NOC scenarios: sat_down, offline, gpu_hot, intrusion, flood, drone_patrol.).
- Use Probe / Save / Send (or the primary button on the page) and watch status chips.
- Empty / fail: Check Admin basics env vars, JWT/
API_TOKEN, TLS insecure for lab certs, and backend reachability. - Success: Status shows healthy / accepted; related Lab or Logs surfaces reflect the change.
Never publish lab IPs — use <host>.