# Pipeline.ecs\_compatibility WARN logs **URL:** \ **Category:** Logstash\ **Tags:** ecs-elastic-common-schema\ **Created:** [December 16, 2021, 1:49pm UTC](https://discuss.elastic.co/t/pipeline-ecs-compatibility-warn-logs/292164 "2021-12-16T13:49:58Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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 16, 2021, 3:27pm UTC](https://discuss.elastic.co/t/pipeline-ecs-compatibility-warn-logs/292164/2 "2021-12-16T15:27:34Z")
The log message occurs during plugin startup, for any plugin attempting to determine what mode it should be initialized in (not just output plugins), when neither the plugin or the pipeline that it is run in declare what mode it should be run in. To silence the deprecation warning for an entire pipeline, you can address it by setting the pipeline-level setting. The value `disabled` locks in the current default behaviour. > [@Warning 'Relying on default value of \`pipeline.ecs\_compatibility' after updating to logstash 7.16.1](https://discuss.elastic.co/t/warning-relying-on-default-value-of-pipeline-ecs-compatibility-after-updating-to-logstash-7-16-1/292018/3): > > 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/pipeline-ecs-compatibility-warn-logs/292164)._