Device Logs
The Device Logs tab in the device detail view gives you visibility into what is happening on a device in real time. There are multiple log sources available depending on your organization's configuration.
Log types
Use the dropdown at the top of the Logs tab to select which log source to view.
Telemetry logs
Telemetry logs are portal-level event records generated by the platform as it manages your devices. They capture things like:
- Enrollment and provisioning events
- Skill deployment and sync events
- Tunnel open/close events
- Errors reported by the portal
Telemetry logs are useful for understanding the history of actions taken on a device — for example, when a skill was last deployed, or whether a deployment succeeded.
These logs auto-refresh every 10 seconds and support infinite scroll for loading older entries.
Hardware logs
Hardware logs are the runtime logs produced by the device's on-board management software. They include:
- Module start, stop, and crash events
- Container runtime messages
- Low-level device and orchestration errors
Hardware logs are pulled directly from the device on demand and refresh every 5 seconds. They are useful for diagnosing device-level issues not related to a specific skill.
Skill logs
Skill logs are the output from a specific skill's container (stdout/stderr). Select the skill from the dropdown to see its logs. These are the same logs you would see if you ran docker logs on the skill container.
For skills built with Docker Compose, you can also filter by individual service within the Compose package.
Skill logs refresh every 5 seconds and show up to several hundred lines. They are the first place to look when a skill is not behaving as expected.
Searching and filtering
- Logs are displayed in reverse-chronological order (newest first).
- Use your browser's built-in search (Ctrl+F / Cmd+F) to search within the visible log output.
- Older entries load automatically as you scroll up.
Downloading logs
A Download Logs button is available in the Logs tab header. Clicking it exports the currently visible log output as a file, which you can share with your team or attach to a support request.
Log entry details
Each telemetry log entry contains:
| Field | Description |
|---|---|
| Timestamp | When the event occurred |
| Type | Severity level: INFO, WARN, ERROR, or DEBUG |
| Message | Description of the event |
Tips
- If a skill is crashing or producing unexpected output, start with Skill logs for that skill.
- If the device itself is misbehaving (connectivity issues, module failures), check Hardware logs.
- For a history of portal actions (deployments, enrollments, tunnel activity), use Telemetry logs.
- If logs are not loading, verify the device is Online — hardware and skill logs require the device to be connected.