Zluri fetches valuable data related to user information, computer usage, user groups, and activity details from JAMF Pro to provide insights into the Apple devices used within the organization for effective management and optimization. This article explains how you can validate the Jamf Data in Zluri.

User Data Processing

If an email address is present in the raw data, Zluri processes the following information:

Email
Name
Status
User photo name
User creation time
User Metadata

If there is no email for a user, Zluri processes the following information:

ID
Name
User photo URL
Status
User creation time
User Metadata

Activities Data Processing

If a user is present in both the previous and current sync, indicating activity on consecutive days, the user is identified as active. If a user was listed in the previous sync but is absent in the subsequent sync, signifying no recent activity, the user is identified as inactive.

Activity type: 'signin'
Processing the 'date' field to extract the activity timestamp

How Zluri Fetches the JAMF Pro Data

Zluri retrieves the list of users and computer application usage from JAMF Pro by calling the following APIs:

Status Mapping Logic

Zluri does not get the explicit user application status of the users from JAMF Pro APIs.

All the users who come from the first API data sync and during the consecutive syncs users are present in both the previous and current sync, indicating activity on consecutive days are marked with User Application Status = ‘Active’.
Users listed in the previous sync but absent in the subsequent sync are marked with User Application Status = ‘Inactive’.

How to Validate the Data

Validating the User Data

To export the Users report, log in to JAMF Pro, and click Users in the sidebar.

Note: Refer Users learning page for detailed steps.

Match the data from the report with the ‘Users’ data received from the API.

Validating the Applications Usage Data

To export the applications usage report, log in to JAMF Pro, and click Computers in the sidebar.

Note: Refer Application Usage learning page for detailed steps.

Match the data from the report with the ‘Application Usage’ data received from the API.