Jamf Pro agent

Where Jamf Pro agent keeps its logs

Jamf Pro agent logs to /var/log/jamf.log on macOS.

Paths are printed exactly as Jamf Pro agent writes them. Environment variables like %LOCALAPPDATA% and $XDG_STATE_HOME are never expanded, so a path can be pasted straight into a shell. Where a path differs between installer types or shipping flavours, each one is racked as its own card below - why that happens.

Finding your way around macOS.

How to turn on debug logging for Jamf Pro agent

1. Run policies with verbose output: sudo jamf policy -verbose.
2. To run a single policy verbosely, use sudo jamf policy -event <triggerName> -verbose.
3. Stream JamfDaemon debug messages with log stream --level debug --predicate 'subsystem BEGINSWITH "com.jamf.management.daemon"' --style compact.
4. Stream Self Service+ debug messages with sudo log stream --debug --predicate 'subsystem BEGINSWITH "com.jamf.selfserviceplus"'.

How to collect Jamf Pro agent logs

1. Collect /var/log/jamf.log; follow it live with tail -f /var/log/jamf.log.
2. For package failures, also collect /var/log/install.log.
3. Self Service+ (1.2.0 and later): Choose Help > Collect Troubleshooting Info, or press Shift+Command+L, to save a zip.
4. Self Service+: Export the last hour of its log with log show --info --predicate 'subsystem BEGINSWITH "com.jamf.selfserviceplus"' --last 1h --style compact.