-
Notifications
You must be signed in to change notification settings - Fork 474
[sei] Add checks to avoid overriding event.original if present #8269
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
b8528f5
to
5485e2c
Compare
Package vectra_detect - 1.5.0 containing this change is available at https://epr.elastic.co/search?package=vectra_detect |
Package zeek - 2.20.0 containing this change is available at https://epr.elastic.co/search?package=zeek |
Package zerofox - 1.20.0 containing this change is available at https://epr.elastic.co/search?package=zerofox |
Package zeronetworks - 1.9.0 containing this change is available at https://epr.elastic.co/search?package=zeronetworks |
Package zscaler_zia - 2.16.0 containing this change is available at https://epr.elastic.co/search?package=zscaler_zia |
Package zscaler_zpa - 1.15.0 containing this change is available at https://epr.elastic.co/search?package=zscaler_zpa |
Proposed commit message
Add checks to avoid overriding event.original if present.
On some setups (ie Logstash sends data to
ES
)event.original
might be already present in the event body. Currently most of our integrations do not have a null check for it before trying to set it, leading to errors on these circumstances. By adding the required checks we improve handling in this setups.Checklist
changelog.yml
file.Related issues
event.original
rename/set to avoid issues with Logstash events #8146