How to List Munki Reports Across All Macs
Using Kolide, you can easily view and query Mac Munki Reports across your fleet.
Introduction
This inventory displays a report about the locally installed Munki service on a device. This includes the current installed version of Munki as well as the last status report associated with the device (eg. success = 'true', success = 'false'). Additionally, warning messages may be communicated where the Munki service did not fail completely, but still encountered difficulty.
The Munki project describes itself as:
Munki is a set of tools that, used together with a webserver-based repository of packages and package metadata, can be used by macOS administrators to manage software installs (and in many cases removals) on macOS client machines.
For more information about the Munki project, please refer to its official website: The Munki Project and the GitHub project.
What Mac Munki Report Data Can Kolide Collect?
Kolide's endpoint agent bundles in osquery to efficiently collect Mac Munki Reports from Macs in your fleet. Once collected, Kolide will parse, clean up, and centrally store this data in Inventory for your team to view, query, or export via API.
Kolide meticulously documents every piece of data returned so you can understand the results.
Mac Munki Reports Schema
| Column | Type | Description | |
|---|---|---|---|
| id | Primary Key |
Unique identifier for the object |
|
| device_id | Foreign Key |
Device associated with the entry |
|
| device_name | Text |
Display name of the device associated with the entry |
|
| catalogs | Text |
Comma-separated list of Munki catalogs |
|
| console_user | Text |
User logged in at the console during the Munki run |
|
| display_names | Text |
Comma-separated list of display names from manifests |
|
| display_users | Text |
Comma-separated list of display users from manifests |
|
| ended_at | Timestamp |
Timestamp when the Munki run ended |
|
| included_manifests | Text |
Comma-separated list of included manifests |
|
| manifest_name | Text |
Name of the primary manifest |
|
| munki_errors | Text |
Errors reported during the Munki run |
|
| started_at | Timestamp |
Timestamp when the Munki run started |
|
| success | Boolean |
|
|
| warnings | Text |
Warnings reported during the Munki run |
|
| version | Text |
The text representation of the version |
|
| version_major | Bigint |
|
|
| version_minor | Bigint |
|
|
| version_patch | Bigint |
|
|
| version_subpatch | Bigint |
|
|
| version_pre | Text |
|
|
| version_build | Text |
|
|
| collected_at | Timestamp |
Time the row of data was first collected in the database |
|
| updated_at | Timestamp |
Time the row of data was last changed in the database |
|
Why Should I Collect Mac Munki Reports?
IT and Security Administrators can review this inventory to verify the installed Munki client on a device is functioning as expected and not encountering errors.
End-User Privacy Consideration
Kolide practices Honest Security. We believe that data should be collected from end-user devices transparently and with privacy in mind.
When you use Kolide to list Mac Munki Report data from end-user devices, Kolide gives the people using those devices insight into exactly what data is collected, the privacy implications, and who on the IT team can see the data. This all happens in our end-user privacy center which can be accessed directly by employees.
