# Warning 'Relying on default value of \`pipeline.ecs\_compatibility' after updating to logstash 7.16.1

**URL:** <https://discuss.elastic.co/t/warning-relying-on-default-value-of-pipeline-ecs-compatibility-after-updating-to-logstash-7-16-1/292018>\
**Category:** Logstash\
**Tags:** docker\
**Created:** [December 15, 2021, 4:42pm UTC](https://discuss.elastic.co/t/warning-relying-on-default-value-of-pipeline-ecs-compatibility-after-updating-to-logstash-7-16-1/292018 "2021-12-15T16:42:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [December 15, 2021, 8:29pm UTC](https://discuss.elastic.co/t/warning-relying-on-default-value-of-pipeline-ecs-compatibility-after-updating-to-logstash-7-16-1/292018/3 "2021-12-15T20:29:23Z")

</div>

When the option isn't specified for an individual plugin, it checks the pipeline-level setting. When the pipeline-level setting is _also_ not specified, you get this warning (not an error).

If you want to _lock in_ the current behaviour for _all_ plugins in a pipeline, add `pipeline.ecs_compatibility: disabled` to its definition in your `config/pipelines.yml`. If you want to do so globally, for all pipelines, add `pipeline.ecs_compatibility: disabled` to your `config/logstash.yml`.

---

_[View the full topic](https://discuss.elastic.co/t/warning-relying-on-default-value-of-pipeline-ecs-compatibility-after-updating-to-logstash-7-16-1/292018)._
