-
Notifications
You must be signed in to change notification settings - Fork 464
[Crowdstrike] Parse prevented
and worker_node_name
field for alert data streams
#14026
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
Conversation
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
@moxarth-rathod, just one query, how were the logs generated ? |
@ShourieG since the original event wasn’t provided, I've created a log based on the issue description. |
Can we get by with deriving this from the last event that already exists in the test sample? It is much shorter and would still exercise the change here. |
Agree with Dan here, if its possible to retrofit the new attributes in the existing smaller log then it would be good in reducing the overall footprint of the change. |
💚 Build Succeeded
History
|
|
Package crowdstrike - 1.73.0 containing this change is available at https://epr.elastic.co/package/crowdstrike/1.73.0/ |
…t data streams (elastic#14026) crowdstrike: request for parsing additional fields. This PR parses `prevented` and `worker_node_name` fields for alert data streams.
Proposed commit message
Checklist
changelog.yml
file.How to test this PR locally