The Agent logs tab lets you get a device's logs from the Swif console, to troubleshoot problems such as apps that don't install, policies that don't apply, or a device that stops checking in. You don't need to ask the user to send logs, or run commands on the device.
It works on macOS, Windows, Linux, and Android devices. Getting logs is read-only: it doesn't change anything on the device.
Who can use it: admins with the Team admin or support role.
Open a device's logs
In Swif, go to Device Management > Device Inventory, and open the device.
Open the Agent logs tab.
The tab shows when the device last sent its logs, as Last reported on, and lists each log it sent:
Column | Shows |
Log | The log's name, and where it is on the device |
Size | The log's size. Click the column to sort by size. |
To download a log, click the download button at the end of its row.
Get the latest logs
Devices send their logs only when you ask. They don't send them on a schedule, so the logs shown are from the last time someone refreshed.
Click the refresh button, next to Last reported on.
Swif asks the device to send its current logs. When they arrive, Last reported on updates.
The device needs to be online. If it's offline, it sends its logs the next time it connects. Devices usually respond to requests from Swif within 2 minutes.
Which logs are collected
macOS
Log | What it's for |
| The Swif agent's main log |
| The Swif agent's output and errors |
| App installs and updates from Swif |
| macOS's own record of package installs |
Windows
Log | What it's for |
| The Swif agent's main log |
| App installs and updates from Swif |
Chocolatey and Windows installer logs | Package installs |
Linux
Log | What it's for |
| The Swif agent's main log |
APT, DNF, or Pacman logs, depending on the distribution | Package installs |
Android
Works on BYOD devices, with a work profile, and on company-owned devices, including fully managed and COPE devices.
The Swif Android app's logs
System logs (Logcat) for the Swif app only. Logs from other apps aren't collected.
A history of when the Swif app stopped or restarted, in
exit-history.json
Before you share logs
Logs can include details from the device, such as usernames, app names, and file paths. Handle them like other device information, and only share them with people who need them, such as Swif support.
Troubleshooting
The Agent logs tab is empty
No one has asked the device for its logs yet. Devices only send logs when you click the refresh button. Click it, and check that the device is online.
The logs are old
Logs aren't sent automatically. Check Last reported on, then click the refresh button to get the current logs.
Last reported on doesn't update after I refresh
Check that the device is online. Offline devices send their logs when they next connect.
Wait a minute, then refresh the page.
On Android, check that the Swif app is installed and running.
A log I expected isn't listed
Logs that don't exist on the device aren't listed. For example, a package manager log appears only if that package manager is used on the device.
I need help reading a log
Download the log, and send it to Swif support, with the device's name or serial number, and what went wrong.
Related resources
