https://docs.edgelq.com/learn/os/operations/ Recent content on SPEKTRA Edge Hugo en https://docs.edgelq.com/learn/os/operations/os-upgrades/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/operations/os-upgrades/ OS upgrades You upgrade a device’s operating system by setting the OS version you want; the device downloads the new version, switches to it, and reboots. Because the system image is separate from your configuration and data, your setup is preserved across the change, and you can roll back to a previous version. How upgrades work You set the target OS version for a device (or a group of devices) from the dashboard. https://docs.edgelq.com/learn/os/operations/reboot-recovery/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/operations/reboot-recovery/ Reboot, shutdown & recovery This page covers power actions you can take remotely and the options for recovering a device that is not behaving as expected. Reboot and shutdown You can reboot or shut down a device remotely from the dashboard or with the cuttle command-line tool. These actions are carried over the device’s connection to the platform and require no inbound access to the device. A device that loses power or is reset returns to its configured state on next boot, because configuration and data are persistent and the system image is read-only. https://docs.edgelq.com/learn/os/operations/logging/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/operations/logging/ Logging Devices can forward their logs to the SPEKTRA Edge platform and you can also pull logs on demand. This lets you observe devices and workloads without logging into each one. Forwarding logs to the platform You can configure a device to forward its system logs and its container (workload) logs to the platform. The logging configuration lets you control: the minimum severity to forward, so you can keep volume manageable which system components to include whether container logs are exported Forwarded logs are available on the dashboard and through the cuttle command-line tool. https://docs.edgelq.com/learn/os/operations/health-checks/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/operations/health-checks/ Health checks Health checks let a device continuously verify that it — or something running on it — is healthy, and report the result to the platform. You define health checks from the dashboard (or the API). Types of checks You can define host-level checks of several types: Type Verifies HTTP An HTTP endpoint responds as expected. TCP A TCP port accepts a connection. gRPC A gRPC service reports healthy. ICMP A host responds to ping. https://docs.edgelq.com/learn/os/operations/status-indicators/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/operations/status-indicators/ Status & indicators A device reports its state both to the platform and, on supported hardware, through a physical LED. This page explains how to read each. Connection status On the platform, a device is shown as: Status Meaning Online The platform detects the device as connected. Offline The device is not detected, or is detected as disconnected. Device information and metrics The device reports details and resource usage you can view on the dashboard, including: https://docs.edgelq.com/learn/os/operations/hooks/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/operations/hooks/ Boot & shutdown hooks Hooks let you run your own scripts at defined points in the device lifecycle — for example to prepare hardware, mount a special device, or clean up on shutdown. They are the supported way to extend device behavior without modifying the read-only system image. Available hooks You can provide a script for each of these points: Hook Runs On boot Early in startup, before the device agent starts. https://docs.edgelq.com/learn/os/operations/workloads/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/operations/workloads/ Running workloads Devices run your applications as containers. You deploy and manage them from the SPEKTRA Edge platform; this page covers only how workloads interact with the OS. For the full application deployment workflow, see the Deploy guide. How workloads use device storage Container images and workload data live on the device’s data area, which uses most of the disk. A workload can mount paths from the device into its containers when it needs access to host data or hardware.