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.
What does this PR do?
This PR is a clean backport of #12305 to 7.x:
Why is it important/What is the impact to the user?
This is a part of an ongoing effort to add ECS Compatibility modes to Logstash plugins (#11635), and to have them on-by-default in the next major release of Logstash (#11623). The newly-introduced
pipeline.ecs_compatibility
allows a user to explicitly control the default behaviour of all plugins in a pipeline.This allows a user on Logstash 7.last to "lock in" a specific behaviour in advance of upgrading to Logstash 8.
Checklist
How to test this PR locally
The only plugin with ECS Compatibility that is currently shipped is the Elasticsearch Output, whose behaviour is changed to use ECS-compatibile index templates. Configure a pipeline that uses it, and run Logstash with
--pipeline.ecs_compatibility=v1
set (command line) orpipeline.ecs_compatibility: v1
(config, eitherlogstash.yml
or under a specific pipeline inpipelines.yml
). Observe ECS-compatible templates being sent to Elasticsearch at startup.