Skip to content

entityanalytics_ad: add support for device entities #14223

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

efd6
Copy link
Contributor

@efd6 efd6 commented Jun 16, 2025

Proposed commit message

entityanalytics_ad: add support for device entities

The data stream is split to do this, essentially in the same way that
the entityanalytics_okta integration move from v1 to v2 was managed.

The pipeline is split into three with calls to a common pipeline. The
third, non-user/non-device pipeline is intended to act as a fallback.
Currently, the differentiated pipelines are largely identical, but the
separation allows easier adjustment in the future.

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

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@efd6 efd6 self-assigned this Jun 16, 2025
@efd6 efd6 added enhancement New feature or request Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] Integration:entityanalytics_ad Active Directory Entity Analytics labels Jun 16, 2025
@efd6 efd6 force-pushed the 13915-entityanalytics_ad branch from d0a44f9 to 1218ee5 Compare June 16, 2025 02:45
@efd6
Copy link
Contributor Author

efd6 commented Jun 16, 2025

/test

The data stream is split to do this, essentially in the same way that
the entityanalytics_okta integration move from v1 to v2 was managed.

The pipeline is split into three with calls to a common pipeline. The
third, non-user/non-device pipeline is intended to act as a fallback.
Currently, the differentiated pipelines are largely identical, but the
separation allows easier adjustment in the future.
@efd6 efd6 force-pushed the 13915-entityanalytics_ad branch from 1218ee5 to 48136ff Compare June 16, 2025 21:50
@elasticmachine
Copy link

elasticmachine commented Jun 16, 2025

💔 Build Failed

Failed CI Steps

History

cc @efd6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:entityanalytics_ad Active Directory Entity Analytics 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.

entityanalytics_ad: allow configuration of device entitly collection
2 participants