Device Registration

Complete onboarding — from monozu edge register to telemetry and command polling.

End-to-end flow

sequenceDiagram
    participant Tech as Technician
    participant CLI as monozu edge register
    participant API as Cloud Backend
    participant Staff as Internal assign API
    participant DB as Azure SQL
    participant Edge as edgezu-agent
    participant Ingest as Ingestor

    Tech->>CLI: Run on appliance
    CLI->>API: POST /v1/devices/announce
    API->>DB: device_claims pending
    API-->>CLI: claim_code XXX-XXX
    Staff->>API: POST /internal/devices/assign
    Note right of Staff: Bearer internal token; Management UI TBD
    API->>DB: device row, claim assigned
    CLI->>API: claim-status then claim-complete
    API-->>CLI: device_id, api_key
    CLI->>Edge: Start agent

    loop Operations
        Edge->>API: GET /v1/commands
        Edge->>Ingest: POST /v1/ingest
    end

Path note

Edge clients use /v1/... on the cloud base URL. Backend Fiber mounts the same handlers under /api/v1/.... See Edge registration.

Post-registration visibility

UI	Who	What
Management	Staff	Fleet sync exists; claim-assign UI not shipped — use POST /internal/devices/assign
Cloud SPA	Tenant	Devices via /api/v1/edge/devices

Online: last_seen_at within 90 seconds.

Security

• Claim code only on device terminal; pending list does not expose codes.
• claim_token hashed server-side; resume file mode 0600.
• Cross-IP re-announce rejected for same hw_serial.

Related

• Edge registration detail
• Runbook

Historical (removed)

Registration keys, POST /api/v1/devices/register, edgezu-tui.