Skip to content

Service status Jamf Pro extension attribute #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 5, 2024

Conversation

ghost
Copy link

@ghost ghost commented Feb 29, 2024

I made a quick script to get the status of Outset and return it as an extension attribute. I'm using this alongside a smart group to determine if any services are somehow disabled by a local user.

@bartreardon bartreardon changed the base branch from main to dev_4.1.2 February 29, 2024 07:43
@bartreardon
Copy link
Contributor

While this will tell you the state of the services it's a bit raw. Could we consider cleaning it up into a "Healthy/Not Healthy" type status instead?

e.g. if any of the agents return something other than Enabled then the EA will indicate it with a simple value, rather than show the raw output of --service-status.

@ghost
Copy link
Author

ghost commented Mar 5, 2024

The script now counts the number of enabled services, which should equal 6. If all services are enabled it will report "Healthy" otherwise it will return "Not Healthy"

@bartreardon
Copy link
Contributor

nice - yeah, we can assume that all 6 need to be loaded for "healthy". If an admin has different needs for their environment they can craft their own EA 🙂

@bartreardon bartreardon merged commit 2ecc76f into macadmins:dev_4.1.2 Mar 5, 2024
@ghost ghost deleted the jamfpro-ea branch March 27, 2024 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants