ECS Compatiblity #57
Open
ECS Compatiblity #57
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does several things to facilitate ease-of-use with Logstash's ECS Compatibility mode
targetoption, allowing users to configure where on the event a records fields should be placed. This option is validated using the Validator Support Mixin's:field_referenceadapter.ecs_compatibilityoption is present via the ECS Compatibility Support Mixin, and warns when the plugin is started in an ECS Compatibility mode without specifying a target.:field_referenceadapter when validating its pre-existingtargetoption, causing incorrect configuration to be rejected at startup instead of plugin crashes at runtime.