Cherry-pick #10875 to 7.0: Force ECS options in filebeat pipelines when filebeat version is over 7.0 and ES version is 6.7.X #10930
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
… 7.0 and ES version is 6.7.X (elastic#10875) When using the `user_agent` processor to ingest data from Filebeat 7.0 into Elasticsearch 6.X conflicts appear with ECS user_agent fields, this can be solved by setting `ecs: true` when pipelines are being loaded into Elasticsearch 6.7.0. For minor versions where `ecs` option is not available, pipelines will fail to load. Fix elastic#10655 (cherry picked from commit 34eaf57)
sayden
approved these changes
Feb 25, 2019
|
jenkins, test this please |
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.
Cherry-pick of PR #10875 to 7.0 branch. Original message:
When using the
user_agentprocessor to ingest data from Filebeat 7.0into Elasticsearch 6.X conflicts appear with ECS user_agent fields, this can
be solved by setting
ecs: truewhen pipelines are being loaded intoElasticsearch 6.7.0.
For minor versions where
ecsoption is not available, pipelines will failto load.
Fix #10655