Skip to main content

Device View and Tabs

The Device view is your single-device operations hub. Access it from Devices > select a device. Each tab provides focused controls and insights. Below is a comprehensive guide to actions, outputs, and tips for every tab.

Tabs (complete)

  • Overview: This tab provides a high-level view of the device’s current status, including online/offline health, the installed Agent version (and whether updates are available), and key telemetry such as CPU and memory usage. It also displays all containers and their states (running, stopped, etc.), along with recent events so you can quickly review deployment history. Additionally, the Overview offers quick device actions such as restart, shutdown, and starting a tunnel.
  • Telemetry: Charts for CPU, memory, disk. Choose time ranges (last hour/day/week). Toggle series and smoothing. Click Report on each chart to export CSV/PDF of the visible time range.
  • Containers: View all containers with their states, images, and health.
    • Actions: Start/Stop/Restart, Logs , Exec/Terminal (TTY/non‑TTY), Inspect (env, mounts, ports, image digest).
  • Terminal: Open an in‑browser shell on the device host (not inside a specific container).
    • Requirements: Agent installed with Terminal enabled; network policy must allow interactive sessions.
    • Auditing: Sessions are recorded in Events with user and timestamps.
    • Safety: Prefer non‑root; elevate per command with sudo. Avoid leaving background jobs running.
  • Files: Browse, upload, download, and delete files/folders on the device (if enabled).
    • Transfers: Upload/download files from the file browser.
    • Create: create new files/folders.
    • copy/move: copy or move files to other directories
    • delete: delete files from the device
    • Metadata: View size, modified time, owner, and permissions.
  • Processes: Real‑time process list similar to ps/top.
    • Columns: PID, user, CPU%, MEM%, start time, command.
    • Troubleshooting: Correlate CPU/memory spikes with Telemetry and recent Events (deployments, updates).
  • Variables: Device‑level variables and secrets that can override project/template defaults during deployments.
    • Manage: Add/edit key/value; mark as secret to redact values in UI and logs.
    • Precedence: Device variable > Deploy‑time input > Template default.
    • Apply from Template: From a Template, use Apply (Variables) to seed missing keys on this device without overwriting existing ones by default.
  • Tunnel: Create a secure, on‑demand TCP tunnel from your browser to a service on the device (e.g., a local web UI on port 8080).
    • Open: Specify local port and target host:port on the device. The UI supplies a localhost URL to click.
    • route traffic through the edge device to other hosts on the same subnet.
    • Lifecycle: Active tunnels show timers; Disconnect or closing the tab tears them down.
    • Security: Authenticated per user; open/close is logged in Events. Use briefly for audited access.
  • Alerts: Active and recent alerts for the device (e.g., high CPU, disk nearly full, container unhealthy).
    • Details: Each alert links to the triggering metric/healthcheck and any related Event.
    • Actions: Acknowledge/mute (where supported) to manage noise per device.
    • Tuning: Thresholds are configured globally or per project; device overrides may apply.
  • Scripts: Run predefined or ad‑hoc scripts on this device.
    • Options: Choose interpreter (bash/sh/pwsh), parameters, environment, run‑as user, timeout.
    • Results: View stdout/stderr and exit code; download logs/artifacts when available.
    • Safety: Prefer idempotent scripts; mark sensitive params as secret so they are redacted in Events.
  • Uptime: Historical online/offline timeline and availability calculations; hover for precise intervals and export.
  • Events: Device-scoped events and audit logs. Clicking opens details and per-step logs (e.g., deployment phases).

Notes and tips

  • Use tags to target batch operations and deployments; keep them accurate and minimal.
  • For container debugging, prefer Exec/Terminal inside a container; use host Terminal for OS‑level issues.
  • Confirm effective configuration with Inspect (container) and Variables (device) before restarting or redeploying.