This screen manages the devices (Edge) installed in factories and on site. A device connects to the platform with the Edge SDK, periodically sends a heartbeat (a sign that it is alive, with CPU and memory usage), uploads collected data, inference results and files, and fetches and runs the commands the platform sends.

Every member can view; restart, Offline, sending commands and viewing logs need operate (OPERATOR, ADMIN), and registering and deleting devices, editing locations, tokens and policy need settings (ADMIN).

Device list

Edge Fleet — ① search ② status filter ③ register a device ④ status ⑤ backlog ⑥ sync
#AreaDescription
SearchFind by device name or location.
Status filterAll · Pending · Healthy · Unhealthy · Uninstalled (전체 · 연결 대기 · 정상 · 비정상 · 미설치).
Register device (디바이스 등록)Registers a new device and issues a token (settings).
Status (상태)Device status. A device blocked at the server also gets a red Blocked (Offline) (Offline 차단됨).
BacklogNumber of items piled up on the device and not sent yet. If any items were dropped for exceeding the retention limit in the last 24 hours, a red −N is attached.
Sync (동기화)The device's transfer state — Idle · Sending · Paused · Offline · Auth failed (대기 · 전송 중 · 일시정지 · 오프라인 · 인증 실패).

CPU, GPU and MEM are the usage from the last heartbeat. Click a row to open the device detail.

Register a device

  1. Press Register device (디바이스 등록).
  2. Enter the device ID (디바이스 ID) (required) and location (위치) (optional), and choose the token scopes (스코프) (what the token is allowed to do) — telemetry (heartbeats, collected records), inference (inference results), container (pulling images), model (model lookup), file (uploading files piled up while offline). All are on by default.
    Register a device — ID, location and token scopes; the token is shown only once
  3. When you press Register (등록), the device token is shown only once. Copy it into the device's configuration. Once you close the window you cannot see it again; if you lose it, you must rotate the token.

Device detail — Overview

Device overview — ① status and live indicator ② Restart, Offline, Delete ③ tabs ④ device info ⑤ resources ⑥ backlog ⑦ token management
#AreaDescription
TitleDevice ID, status, Live (실시간) (changes show up at once) or Polling 10s (폴링 10초), and N pending commands (대기 명령 N) if there are commands not yet fetched.
ActionsRestart (재시작) (operate), Offline (Offline) (operate, blocks at the server), Delete (삭제) (settings; enabled only after live tokens are revoked).
TabsOverview (개요) · Collected data (수집 데이터) · Inference results (추론 결과) · Files (파일) · Commands (명령) · Policy (정책).
Device info (디바이스 정보)OS, SDK and agent versions, location (Edit location (위치 편집)), last heartbeat, policy revision (the policy version number; shows whether the device has applied the new policy).
ResourcesCPU, GPU, MEM and DISK usage (refreshed every 30 seconds).
Backlog (쌓인 데이터)Pending count and size, oldest item, dropped in 24 hours, sync state, last transfer.
Token management (토큰 관리)Rotate (회전) (issue a new token — shown only once), Revoke (회수) (discard the token), view and edit scopes (settings).

There are also Local models (로컬 모델) (models downloaded to the device and the version running — switch with Switch to this version (이 버전으로 전환)), Collectors (수집기), Containers (컨테이너) and Logs (recent heartbeats) (로그(최근 하트비트)) (operate) cards.

Other tabs

Collected data (수집 데이터) — structured records the device uploaded (time, kind, priority, payload). New records keep arriving; turn off Follow latest (최신 고정) to freeze the list so you can read it slowly. Filter by kind with the select box at the top.

Collected data tab — records sent by the device (time, kind, priority, payload)

Inference results (추론 결과) — time, model, latency (ms) and result (JSON) of inferences run on the device.

Inference results tab — time, model, latency and result

Files (파일) — files that piled up while offline and were then uploaded, with transfer state, chunk progress and linked dataset.

Files tab — files uploaded after being queued offline, with transfer state

Commands (명령) — commands sent to the device and their results. The device is behind NAT and the server cannot connect to it first, so a command goes into a queue and the device fetches it the next time it asks.

Commands tab — ① command type (ping, restart, resync, pull model) ② send; sent commands and their state below
#AreaDescription
Command typePing () (check that it is alive), Restart (재시작) (restart the agent), Resync (재동기화) (put items that were folded as failed back into the send queue), Pull model (모델 내려받기) (choose a model name and version to download and activate).
Send command (명령 보내기)Puts the command in the queue (operate).

Policy (정책) — the device's behavior settings. Only ADMIN can change them; saving increments the policy revision (its version number), and the device notices the change in its next heartbeat response and fetches the new policy.

Policy tab — heartbeat interval, retention, transfer limits and more. ① Save policy (ADMIN)
ItemDefaultDescription
Heartbeat interval (s) (하트비트 주기 (초))30Must be well below the server's offline threshold (180 seconds).
Retention period (days) (보존 기간 (일))300 means no limit.
Retention size (GiB) (보존 용량 (GiB))50When exceeded, items with the lowest priority and oldest age are dropped first.
Transfer rate limit (B/s) (전송 속도 상한 (B/s))00 means unlimited.
CPU pause threshold (%) (CPU 일시정지 임계 (%))85Transfers pause when CPU exceeds this value. 0 disables the check.
Allowed transfer windows (전송 허용 시간대)(empty)Empty means always. Example: 22:00-06:00 (separate several with commas).

Statuses and badges

Device status:

BadgeValueMeaning
Pending (연결 대기)PENDINGRegistered, but no heartbeat has ever arrived
Healthy (정상)ACTIVEA heartbeat arrived within the last 180 seconds
Unhealthy (비정상)UNHEALTHYThe last heartbeat is older than 180 seconds. A WARNING alert is then created; when heartbeats arrive again, the device returns to Healthy and the alert clears by itself.
Uninstalled (미설치)UNINSTALLEDMarked as a device whose installation was removed

Command status:

BadgeValueMeaning
Queued (대기 중)queuedWaiting for the device to fetch it
Delivered (전달됨)deliveredThe device fetched it
Completed (완료)ackedThe device reported success
Failed (실패)failedThe device reported failure
Expired (만료)expiredNot fetched within 24 hours (a device that was off for a long time)

File transfer status: Transferring · Assembling · Completed · Failed (전송 중 · 조립 중 · 완료 · 실패). A file that stays in transferring for 7 days turns into failed.

Offline blocking

When you want to cut a device off for a while (maintenance, suspicious behavior), press Offline (Offline) on the overview.

Offline confirmation — the server refuses all requests from the device; it queues data, so nothing is lost

Written for the platform as of 2026-09-21.

© Geo-MLOps