-
Notifications
You must be signed in to change notification settings - Fork 442
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
nagios_xi: fix handling of potentially null method call receivers #9003
Conversation
🚀 Benchmarks reportTo see the full report comment with |
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
@@ -681,7 +703,7 @@ processors: | |||
|
|||
- remove: | |||
field: event.original | |||
if: "ctx?.tags == null || !(ctx.tags.contains('preserve_original_event'))" | |||
if: "ctx.tags == null || !(ctx.tags.contains('preserve_original_event'))" |
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.
Can we also make this change in the events
datastream? This way the change becomes consistent across all datastreams.
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.
Stretching scope, but done.
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!
💚 Build Succeeded
History
cc @efd6 |
Package nagios_xi - 1.2.1 containing this change is available at https://epr.elastic.co/search?package=nagios_xi |
Proposed commit message
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
null
handling inif
conditions and elsewhere #8646Screenshots