Skip to content

Jamf Pro: add support for ECS entity fields#18503

Draft
chemamartinez wants to merge 9 commits intoelastic:mainfrom
chemamartinez:18293-jamf_pro-entity-fields
Draft

Jamf Pro: add support for ECS entity fields#18503
chemamartinez wants to merge 9 commits intoelastic:mainfrom
chemamartinez:18293-jamf_pro-entity-fields

Conversation

@chemamartinez
Copy link
Copy Markdown
Contributor

Proposed commit message

Adds ECS entity field support to the Jamf Pro integration for both
the inventory and events data streams.

Maps managed status, OS version, last activity timestamp, group
memberships, and local admin accounts to host.entity.* and
user.entity.* fields:

- host.entity.attributes.managed from general.remote_management.managed
- host.os.* (name, version, full, platform) moved from standalone
  os.* to the host.os.* namespace in both pipelines
- host.entity.lifecycle.last_activity from general.last_contact_time
  (inventory) and webhook.event_timestamp (events)
- user.group.id and user.group.name from group_memberships[*].
  It requires the GROUP_MEMBERSHIPS section to be enabled.
- user.entity.attributes.administered_by from local_user_accounts[*]
  where admin == true, collecting {user_id, username, email} per entry.
  It requires the LOCAL_USER_ACCOUNTS section to be enabled.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

@chemamartinez chemamartinez self-assigned this Apr 17, 2026
@chemamartinez chemamartinez added enhancement New feature or request Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] Integration:jamf_pro Jamf Pro labels Apr 17, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 17, 2026

Vale Linting Results

Summary: 6 warnings found

⚠️ Warnings (6)
File Line Rule Message
packages/jamf_pro/docs/README.md 204 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/jamf_pro/docs/README.md 205 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/jamf_pro/docs/README.md 206 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/jamf_pro/docs/README.md 511 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/jamf_pro/docs/README.md 512 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/jamf_pro/docs/README.md 513 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

Comment thread packages/jamf_pro/changelog.yml
@andrewkroh andrewkroh added the documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. label Apr 17, 2026
@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

History

cc @chemamartinez

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Integration:jamf_pro Jamf Pro Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Jamf Pro: add support for entity fields

3 participants