Introduction
The tags beginning with mdm.jamf identify events generated by Jamf.
The full tag must have four levels. The first two are fixed as mdm.jamf and represent technology and brand. The third level corresponds to the service while the fourth identifies the type of events sent.
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service | Tags | Data tables |
|---|
Jamf Pro Mobile Device Management (MDM) | mdm.jamf.events
| mdm.jamf.events
|
mdm.jamf.pro
| mdm.jamf.pro
|
mdm.jamf.pro.computer_added
| mdm.jamf.pro.computer_added
|
mdm.jamf.pro.computer_checkin
| mdm.jamf.pro.computer_checkin
|
mdm.jamf.pro.computer_inventory_completed
| mdm.jamf.pro.computer_inventory_completed
|
mdm.jamf.pro.computer_patch_policy_completed
| mdm.jamf.pro.computer_patch_policy_completed
|
mdm.jamf.pro.computer_policy_finished
| mdm.jamf.pro.computer_policy_finished
|
mdm.jamf.pro.computer_push_capability_changed
| mdm.jamf.pro.computer_push_capability_changed
|
mdm.jamf.pro.device_added_to_dep
| mdm.jamf.pro.device_added_to_dep
|
mdm.jamf.pro.jss_shutdown
| mdm.jamf.pro.jss_shutdown
|
mdm.jamf.pro.jss_startup
| mdm.jamf.pro.jss_startup
|
mdm.jamf.pro.mobile_device_checkin
| mdm.jamf.pro.mobile_device_checkin
|
mdm.jamf.pro.mobile_device_command_completed
| mdm.jamf.pro.mobile_device_command_completed
|
mdm.jamf.pro.mobile_device_enrolled
| mdm.jamf.pro.mobile_device_enrolled
|
mdm.jamf.pro.patch_software_title_updated
| mdm.jamf.pro.patch_software_title_updated
|
mdm.jamf.pro.push_sent
| mdm.jamf.pro.push_sent
|
mdm.jamf.pro.rest_api_operation
| mdm.jamf.pro.rest_api_operation
|
mdm.jamf.pro.scep_challenge
| mdm.jamf.pro.scep_challenge
|
How is the data sent to Devo?
You can use the HTTP endpoint to ingest data into these tables.
Table structure
These are the fields displayed in these tables:
