Introduction
The tags beginning with mdm.jamf identify events generated by Jamf.
Valid tags and data tables
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.
Technology | Brand | Service | Type |
|---|---|---|---|
mdm | jamf | pro |
|
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
|---|---|
mdm.jamf.pro.mobile_device_push_sent | mdm.jamf.pro.mobile_device_push_sent |
mdm.jamf.pro | mdm.jamf.pro |
mdm.jamf.pro.mobile_device_unenrolled | mdm.jamf.pro.mobile_device_unenrolled |
mdm.jamf.pro.device_added_to_dep | mdm.jamf.pro.device_added_to_dep |
mdm.jamf.pro.computer_checkin | mdm.jamf.pro.computer_checkin |
mdm.jamf.pro.mobile_device_enrolled | mdm.jamf.pro.mobile_device_enrolled |
mdm.jamf.pro.jss_startup | mdm.jamf.pro.jss_startup |
mdm.jamf.pro.computer_policy_finished | mdm.jamf.pro.computer_policy_finished |
mdm.jamf.pro.computer_added | mdm.jamf.pro.computer_added |
mdm.jamf.pro.jss_shutdown | mdm.jamf.pro.jss_shutdown |
mdm.jamf.pro.computer_patch_policy_completed | mdm.jamf.pro.computer_patch_policy_completed |
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.patch_software_title_updated | mdm.jamf.pro.patch_software_title_updated |
mdm.jamf.pro.computer_push_capability_changed | mdm.jamf.pro.computer_push_capability_changed |
mdm.jamf.pro.scep_challenge | mdm.jamf.pro.scep_challenge |
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.computer_inventory_completed | mdm.jamf.pro.computer_inventory_completed |
How to ingest data?
To ingest data you can use the HTTP endpoint.