Logs
Logs - how to interpret?
Logs are the simplest way to debug the device. In case of any problems with the device, logs are the first place to look for information about the source of the issue. Logger configuration is done in the settings section.
Log Viewer
The boneIO log viewer offers advanced features for analysis and diagnostics.
Log Level Filtering
Logs can be filtered by severity level:
| Level | Description |
|---|---|
| ERROR | Critical errors requiring immediate attention. |
| WARNING | Warnings about potential problems. |
| INFO | Normal operation information. |
| DEBUG | Detailed diagnostic information — visible only with debug mode enabled. |
Filtering is server-side — only logs at the selected level are fetched, significantly speeding up browsing.
Module Filtering
Logs can also be filtered by source module (e.g. boneio.webui.app, boneio.core.manager). This allows focusing on logs from a specific controller component. Available modules are automatically detected from incoming logs.
Date Filtering
Date range selection allows narrowing displayed logs to a specific time period. Useful for analyzing historical events.
Infinite Scroll
The log viewer uses cursor-based pagination with infinite scroll. New logs are automatically loaded as you scroll — no manual page navigation required.
Selection and Copy
Logs can be selected by clicking individual rows:
- Shift+click — select a range
- Drag selection — select multiple rows by dragging
Selected logs can be:
- Copied to clipboard — in text format
- Shared to Discord — copied in code block format (
```log ```) ready for pasting on the boneIO Discord channel
Debug Mode Toggle
The Debug button enables temporary runtime log level change — without restarting the controller. After enabling debug mode, DEBUG-level logs start flowing immediately. Debug mode is temporary — it resets on controller restart.
Log level change is done via API: GET/POST /api/log-level.