Backport PR #13612 to 7.17: [Docs] Add pipeline.ecs_compatibility to the list (#13638)

* [Docs] Add pipeline.ecs_compatibility to the list (#13612)

* Add pipeline.ecs_compatibility to the list

* Update docs/static/running-logstash-command-line.asciidoc

Co-authored-by: Ry Biesemeyer <yaauie@users.noreply.github.com>

Co-authored-by: Ry Biesemeyer <yaauie@users.noreply.github.com>
(cherry picked from commit e11d0364d4)

* Rephrase docs for --pipeline.ecs_compatibility flag for 7.x perspective

Co-authored-by: Toby Sutor <55087308+toby-sutor@users.noreply.github.com>
This commit is contained in:
Ry Biesemeyer 2022-01-20 10:52:26 -08:00 committed by GitHub
parent c8e2bef09b
commit 22e2e52d9c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -157,6 +157,15 @@ With this command, Logstash concatenates three config files, `/tmp/one`, `/tmp/t
When creating pipeline batches, how long to wait while polling for the next event. This option defines
how long in milliseconds to wait while polling for the next event before dispatching an undersized batch
to filters and outputs. The default is 50ms.
*`--pipeline.ecs_compatibility MODE`*::
Sets the process default value for ECS compatibility mode.
Can be an ECS version like `v1` or `v8`, or `disabled`.
The default is `disabled`.
In Logstash 8, ECS compatibility will be enabled by default.
To prepare for an upgrade to Logstash 8, you can lock-in the Logstash 7 behavior for an individual pipeline by setting `pipeline.ecs_compatibility: disabled` in its `pipelines.yml` definition. Doing so will ensure that a migrated pipeline will continue to operate as it does in Logstash 7.
Using the command-line flag will set the default for _all_ pipelines, including new ones.
See <<ecs-compatibility>> for more info.
*`--pipeline.unsafe_shutdown`*::
Force Logstash to exit during shutdown even if there are still inflight events