If you use both Jamf and Munki (and specifically use Jamf to deploy Munki or reinstall Munki), you may want to have a Jamf extension attribute to see the health of the last Munki run.

Munki has a file at /Library/Managed Installs/ManagedInstallReport.plist, which stores details about the last run.

Here’s an example of what an extension attribute might look like:
munki_health_check.sh

If you find it useful, feel free to tweak it to suit your organization’s specific needs.

Example output for a health run would be: Last Munki run was 2025-04-20 16:20:49 +0000
<result>Munki healthy</result>

Example unhealthy (can’t retrieve primary manifest) would be: <result>Unhealthy: Could not retrieve managed install primary manifest.:
(-1004, 'Could not connect to the server.')</result>

Example unhealthy (Munki run too long ago) would be: <result>Unhealthy: Last Munki run was 2025-04-12 05:15:57 +0000</result>