Know how many hosts, and which hosts, have Munki issues

[noahtalerman]

Problem

I'm an engineer using Munki to push new software to thousands of macOS hosts and I'm overwhelmed by the amount of issues with Munki I need to address. I want help prioritizing these Munki issues.

Goal

As a Munki admin, add ability to see the most common Munki issues so that I can prioritize resolving the issues that impact the most hosts.

I also want to be able to see which macOS hosts have these issues so that I know which hosts need issues resolved.

Parent epic

• Expansion of host vitals #397

Figma

https://www.figma.com/file/hdALBDsrti77QuDNSzLdkx/%F0%9F%9A%A7-Fleet-EE-(dev-ready%2C-scratchpad)?node-id=7647%3A273670

Child issue

• Add new Munki issues card for MacOS hosts #6931
• Provide Munki issues for MacOS hosts #6961

Documentation

• Specify that in order for this to work, requires Orbit.
• Assumes a specific Munki install and the info is in a specific location.

How?

Inform the user what Munki issues are most common and which hosts have these issues.

We'll use the a Munki error or warning returned by the munki_info table from the macadmins osquery extension to determine distinct issues.

• This osquery query can be used to get all Munki errors on a host: SELECT errors FROM munki_info WHERE errors != ''; Note that this query always returns one result even if there is more than one error. When there is more than one error, The errors column separates each error with a semicolon (;). For example this query will return something like:
  • Could not retrieve managed install primary manifest;A default keychain could not be found
  • We'll want to separate these errors into unique Munki issues in the Fleet UI and API.
• This osquery query can be used to get all Munki warnings on a host: SELECT warnings FROM munki_info WHERE warnings != ''; Like errors, this query always returns one result even if there is more than one warning. When there is more than one error, The warnings column separates each error with a semicolon (;). For example this query will return something like:
  • Could not process item Figma for optional install. No pkginfo found in catalogs: release;Could not process item Zoom for optional install. No pkginfo found in catalogs: default;Could not process item Microsoft Visual Studio Code for optional install. No pkginfo found in catalogs: a really long catalog...
  • We'll want to separate these warnings into unique Munki issues in the Fleet UI and API.

[noahtalerman]

Think about writing a policy/query first.

[noahtalerman]

@lukeheath I passed this issue to you for UI review and specification.

I'm linking to a Loom video in which I demo the UI changes here: https://www.loom.com/share/8080d2743f0c45a5a583e9ea0ae7737e

If you have any questions or feedback while I'm out (July 22 - 31), please don't hesitate to reach out to Mike McNeil. I've asked Mike to be ready to receive these questions.