Prerequisites
Required permissions: Admin or Staff role with access to Fleet > Software Management
Supported platforms: Android, iOS, iPadOS, macOS, Windows
Time estimate: 5–10 minutes to review or export event logs
Additional requirements: Devices must be enrolled and MDM activated to generate logs
Before You Start
Event Logs provide a detailed history of all software-related activities within Trio, including app installations, updates, uninstallations, approvals, and errors. They serve as an essential auditing and troubleshooting tool for IT admins.
Event Logs can be filtered by app, user, event type, or date, and exported for compliance and reporting purposes. Reviewing logs helps identify issues with deployment, track admin actions, and ensure policy compliance across all devices.
Step 1: Access Event Logs
Navigate to Fleet > Software Management.
Select the relevant platform (Android, iOS, iPadOS, macOS, Windows).
Click the Event Logs tab next to Software Library.
Expected result: A chronological list of software-related activities appears.
If you see: An empty log view → Solution: Verify that devices are enrolled and software actions (install, update, etc.) have occurred.
Step 2: Search and Filter Event Logs
Use the search bar to find logs by app name, user, or event type.
Apply filters to narrow down results:
Event name (e.g., App Installed, App Update Failed, Script Executed)
User (admin who performed the action)
Date range
Expected result: Only the filtered logs are displayed.
Troubleshooting this step:
Issue: No logs found → Solution: Clear filters and try again.
Issue: Logs missing → Solution: Confirm logging is enabled and the device is reporting to Trio.
Step 3: View Activity Details
From the log list, click on any activity entry.
A detail panel opens showing:
Event type (e.g., Instance Script Execution, App Updated, Silent Installation Triggered)
Timestamp
User (admin who executed the action)
Admin Role
Optionally, click Download activity log to save the individual record.
Expected result: Detailed context for the selected log entry is visible.
Step 4: Export Event Logs
In the Event Logs view, click Export.
Set the date range for the export.
Choose whether to export with the original columns or customize the fields.
Click Export to download the file.
Expected result: A file containing event log data is downloaded for reporting or compliance.
Troubleshooting this step:
Issue: Export fails → Solution: Ensure pop-ups/downloads are allowed in your browser.
Issue: Incomplete logs in export → Solution: Adjust date range and check filter settings.
Next Steps
Immediate actions:
Review failed installations or outdated apps to trigger updates.
Use event logs to confirm if app assignments succeeded on devices.
Related configurations:
Pair with Software Policy to enforce compliance and monitor enforcement logs.
Use Command Center for real-time troubleshooting when repeated failures occur.
Advanced Options
Drill-Down by User: Track admin-level actions to identify who approved, rejected, or retried software installations.
Audit Trail for Compliance: Use exported logs for compliance audits, security reviews, or vendor reporting.
Cross-Platform Reporting: Combine event logs across Android, iOS, macOS, and Windows for a single compliance view.
Troubleshooting
Symptom: Logs not updating → Cause: Device not syncing. → Solution: Trigger manual sync from device.
Symptom: Certain events missing → Cause: Filters applied. → Solution: Clear all filters.
Symptom: Export shows empty file → Cause: No logs exist in the selected range. → Solution: Adjust date range.
Symptom: User details missing → Cause: Action performed by automated policy. → Solution: Check related Software Policy logs.