[3.x] Add a target field support. (#196) #197
Merged
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.
Introduces a target field as a field reference (mixin validated) where if set result is placed into the target.
Simplifies the set extracted values to the event with target logic. Applies setting to target with aggregations similarly with es-input.
Mention to target in each fields which can be placed in the target. Docs info fields are placed in target field.
(cherry picked from commit 5abbe49)
Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/
Cherry-pick merge conflict files:
CHANGELOG.MD: main vs 3.x logs are always differentlogstash-filter-elasticsearch.gemspec: version conflictfilters/elasticsearch/elasticsearch.rb: due to SSL setting obsoletion which also removed thenormalize_config_support