-
Notifications
You must be signed in to change notification settings - Fork 12
Feat: adjust fields for ECS compatibility #19
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
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 🎉
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.
Minor wording suggestion inline. LGTM pending version bump (required for docs changes to get picked up).
"command" => "echo '¡Hola!'", | ||
"host" => "deus-ex-machina" | ||
} | ||
----- |
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.
Thanks for adding these examples. Nice!
Co-authored-by: Karen Metts <35154725+karenzone@users.noreply.github.com>
Previously plugin was setting the top level
command
andhost
fields for every event (which aren't ECS compliant).There's a change in behavior to not override fields if they exists in the decoded payload (e.g. no longer force the
host
field if such a field is decoded from the command's output).Also avoid an unnecessary
undefined method
close' for nil` when a different thread stops the plugin.Plugin changes are similar to it's input exec cousin: logstash-plugins/logstash-input-exec#28