# Pipeline has lesser fields than Filebeat directly to Elasticsearch

**URL:** <https://discuss.elastic.co/t/pipeline-has-lesser-fields-than-filebeat-directly-to-elasticsearch/269054>\
**Category:** Elasticsearch\
**Created:** [April 1, 2021, 4:04pm UTC](https://discuss.elastic.co/t/pipeline-has-lesser-fields-than-filebeat-directly-to-elasticsearch/269054 "2021-04-01T16:04:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Automation\_Scripts](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/automation_scripts/32/85374_2.png) [@Automation\_Scripts](https://discuss.elastic.co/u/Automation_Scripts)\
**Post date:** [April 1, 2021, 4:04pm UTC](https://discuss.elastic.co/t/pipeline-has-lesser-fields-than-filebeat-directly-to-elasticsearch/269054/1 "2021-04-01T16:04:17Z")

</div>

Hi team,

I have a pipeline like this: filebeat =\>kafka =\>logstask=\>elasticsearch (ELK7.12)

Why I have a smaller amounts of fileds than filebeat directly =\>elasticsearch (ELK7.11.1)

Whenever I check the fields from ECS seems that even the default dashboards from Filebeat -Zeek are not finding correctly all the fields from ECS.

The new version 7.12 ships with smaller fields synchronisation for modules?

Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 29, 2021, 4:04pm UTC](https://discuss.elastic.co/t/pipeline-has-lesser-fields-than-filebeat-directly-to-elasticsearch/269054/2 "2021-04-29T16:04:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.