​

Sessions & Logs

​

Start or find a session

• Device-driven: device starts a session; it appears automatically in Sessions.
• UI-driven (if enabled): start from the device detail page.
• Use filters: device, status (Active/Completed/Failed), date range.

​

Check session details

• Status and duration; capsule/composition (if provided).
• Error/warning counts if available.
• Links: Files (artifacts) and Logs (scoped view).

​

View logs

• Open Logs from the session row or top nav.
• Filters: device, session, module, log level, time range, text search.
• Toggle auto-scroll for live follow; scroll up for older entries (pagination).
• Export filtered logs to CSV/JSON.

​

What “good” looks like

• Session transitions from Active → Completed.
• Logs appear within a second or two of generation.
• No repeated connection errors from the device.

​

Troubleshooting

• No logs: device clock off, batching disabled, or network blocked.
• Gaps in logs: buffer too small or uploads failing—check device-side logs.
• Stuck session: device never sent completion; restart and ensure teardown flushes logs/artifacts.