Logs and diagnostics

Logs are the first line of diagnosis when a device misbehaves in the field. Configure them before devices ship, not after the first support call.

Why device-tied logs matter

Generic log platforms collect streams of data but often lack device identity. When support gets a ticket about "the gateway at site 7," they need logs tied to that specific device - not a search across unrelated streams.

Setup approach

1. Identify the log sources that matter for your application (application logs, systemd journals, custom output)
2. Configure log collection on the device during image build
3. Verify logs appear in the Dataplicity dashboard for a test device
4. Include log configuration in your golden image

Diagnostics on mobile and desktop apps

If Diagnostics is available to your organisation, use it to inspect device hardware and system information.

When to use this

• Application errors need investigation without SSH
• Support wants context before opening a remote shell
• Engineering needs visibility into field behaviour

Related

• Logs concept
• Troubleshooting agent logs