# Filebeat Zeek module doesn’t add ECS fields to zeek logs

**URL:** <https://discuss.elastic.co/t/filebeat-zeek-module-doesn-t-add-ecs-fields-to-zeek-logs/270047>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 13, 2021, 6:08pm UTC](https://discuss.elastic.co/t/filebeat-zeek-module-doesn-t-add-ecs-fields-to-zeek-logs/270047 "2021-04-13T18:08:11Z")\
**Posts on this page:** 4\
**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 13, 2021, 6:08pm UTC](https://discuss.elastic.co/t/filebeat-zeek-module-doesn-t-add-ecs-fields-to-zeek-logs/270047/1 "2021-04-13T18:08:11Z")

</div>

Hi all,

I followed the official documentation and I’ve changed zeek’s output to json logs but somehow zeek module from Filebeat does’t enrich data with ECS fields. Filebeat sends the logs, but without adding the extra fields as per ECS and it’s github code. Just to give you an example there is no event.dataset or source.ip etc.

I’ve enabled zeek module with `sudo filebeat modules enable zeek` and added the log paths to zeek.yml, but the extra fields were not added. Used this blogpost [Collecting and analyzing Zeek data with Elastic Security | Elastic Blog](https://www.elastic.co/blog/collecting-and-analyzing-zeek-data-with-elastic-security)

The fields are called `zeek.id.orig_h ` and not `zeek.connection.id.orig_h ` as per your docs. How can I solve this?

Thank you!

---

<div class="post-metadata">

**Author:** ![Marius\_Iversen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_iversen/32/68988_2.png) [@Marius\_Iversen](https://discuss.elastic.co/u/Marius_Iversen)\
**Post date:** [April 13, 2021, 11:36pm UTC](https://discuss.elastic.co/t/filebeat-zeek-module-doesn-t-add-ecs-fields-to-zeek-logs/270047/2 "2021-04-13T23:36:09Z")

</div>

Hello @Automation_Scripts 🙂

So there is a few things we need to rule out here to find out where the issue might be, if its in our parsing or just a misconfiguration somewhere.

Would you be able to provide a single line from the logfile you are trying to read? And if possible a copy of the filebeat.yml and zeek.yml file? Feel free to remove or obsfucate any sensitive information like usernames and passwords etc.

---

<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 15, 2021, 4:36pm UTC](https://discuss.elastic.co/t/filebeat-zeek-module-doesn-t-add-ecs-fields-to-zeek-logs/270047/3 "2021-04-15T16:36:27Z")

</div>

So the instalation is not quite straight forward, but I managed to run ELK with docker. I think a video demo with the instalation of ELK would help a lot the community.

---

<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:** [May 13, 2021, 6:36pm UTC](https://discuss.elastic.co/t/filebeat-zeek-module-doesn-t-add-ecs-fields-to-zeek-logs/270047/4 "2021-05-13T18:36:30Z")

</div>

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