Find the devices that need attention.
Use reported device health, configuration state, command results, and application rollout status to prioritize investigation. Soar turns selected conditions into notifications and brings fleet statistics into a separate reporting view.
Review a fleet-health workflowIdentify devices that need attention
| Signal | What to inspect |
|---|---|
| Missed reporting | Last seen, network conditions, and time elapsed relative to the expected heartbeat. |
| Low battery | Reported charge and the risk of an interruption. |
| Memory or storage pressure | Resource use alongside device and application activity. |
| Configuration mismatch or error | Expected and reported name/version, update timing, and setting or package errors. |
| Slow or failed command | Target acknowledgements and elapsed time. |
| Application rollout failure | Installation errors in the current batch before continuing. |
Set a useful reporting interval
Configurations set the expected heartbeat interval. Offline notifications allow missed reporting time, with a minimum allowance; a single missed heartbeat does not automatically raise an alert.
Data saving can reduce reporting frequency. Longer intervals also mean older device information between check-ins.
Review fleet trends
Statistics combines current fleet state with historical heartbeat, battery, RAM, storage, and network-traffic data. It also summarizes commands and active application rollouts.
Choose how your team receives updates
Use in-app notifications or email updates for device events.
Incident reporting can capture unhandled exceptions, application-not-responding events, and manual SDK reports, with capture and rate controls.
Incident reporting requires a configured Sentry destination and the matching device or application integration.