-
Notifications
You must be signed in to change notification settings - Fork 456
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
Extract potential host.domain and user.domain in Cisco Secure Endpoint #2888
Extract potential host.domain and user.domain in Cisco Secure Endpoint #2888
Conversation
@P1llus please test :) |
I added some small additions to it, some extra failure checks in the scripts, ran the CI generation of test data, and ensured that both host fields are still set. Just need another to review then I can merge. |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove event.ingested
at https://github.com/elastic/integrations/pull/2888/files#diff-f430f71598ebb4c703c61a0500ebad83a87feee76e6f33c9ec8720576574e01eR38-R40?
None of the host.domain
fields have any value other than "".
packages/cisco_secure_endpoint/data_stream/event/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
elastic#2888) * Extract potential host.domain and user.domain * Bump version to 2.0.1 Bump version * Update changelog.yml * Fixes Needed to use cisco.secure_endpoint.computer.hostname instead of host.name * updating CI tests and adding some minor changes * adding some small modifications to pipeline * adding some small changes based on PR review * update docs Co-authored-by: Marius Iversen <[email protected]>
What does this PR do?
Will try to extract host.domain, user.domain and user.email if possible.
Checklist
changelog.yml
file.