Using Fieldhand
Services and logs
Know when a service on a device stops, and read its log from the browser.
Watched services
In Settings → Watched services, list the systemd or OpenRC services every device should keep running, such as kiosk-app, nginx or chronyd. Each device checks them every minute and reports when one changes. Its page shows each service's state, sub-state, restart count and how long it has been in that state.
| State | Meaning |
|---|---|
| active | Running. |
| failed | Crashed or exited with an error. Alerts. |
| inactive | Stopped. Alerts, since you said it should run. |
| activating | Starting, or restarting in a loop (watch the restart count). |
| not on this device | The service doesn't exist there. Never alerts, so one list fits a mixed fleet. |
A failed or stopped service sends an alert to email and every alert channel, and another when it runs again.
Logs
Logs on a device page, or next to a service, shows the last lines of its journal (journalctl -u) or of any log file (type a path starting with /). With Follow on, new lines appear as they're written, like tail -f; closing the panel stops it on the device.
- Logs are read as the shell user. Reading the journal as a non-root user needs the systemd-journal group.
- Devices without journald (Alpine, BusyBox) use a file path, for example /var/log/messages.
- Each log you open is in the device's activity log.
Something wrong or missing on this page? Tell us.