# Zeek & ELK integration (A lot of strange fields)

**URL:** <https://discuss.elastic.co/t/zeek-elk-integration-a-lot-of-strange-fields/284547>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 18, 2021, 6:34pm UTC](https://discuss.elastic.co/t/zeek-elk-integration-a-lot-of-strange-fields/284547 "2021-09-18T18:34:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![test\_qweqwe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/test_qweqwe/32/94750_2.png) [@test\_qweqwe](https://discuss.elastic.co/u/test_qweqwe)\
**Post date:** [September 18, 2021, 6:34pm UTC](https://discuss.elastic.co/t/zeek-elk-integration-a-lot-of-strange-fields/284547/1 "2021-09-18T18:34:49Z")

</div>

Hi there,  
I set up ELK and then beats on Zeek server to send data to Elasticsearch.  
Everything is good except one: there are a lot of fields - 308

 ![2021-09-18 21_19_24-ELK - VMware Workstation](https://us1.discourse-cdn.com/elastic/original/3X/1/9/199bafe2a425c22a2557b89f6a1de9fe0ff13166.png)  
And it creates an element of inconvenience for me to create a search. I think I've done something wrong, set it up wrong somewhere. There are even fields with the prefix "suricata".  
 ![2021-09-18 21_33_26-ELK - VMware Workstation](https://us1.discourse-cdn.com/elastic/original/3X/d/0/d04f582318b613ef5805a53bd001c10f7b40547c.png)  
How did you send Zeek logs to the ELK? What is your configuration?  
What inputs do you need from me?

---

<div class="post-metadata">

**Author:** ![Iker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iker/32/91708_2.png) [@Iker](https://discuss.elastic.co/u/Iker)\
**Post date:** [September 18, 2021, 7:42pm UTC](https://discuss.elastic.co/t/zeek-elk-integration-a-lot-of-strange-fields/284547/2 "2021-09-18T19:42:13Z")

</div>

Hi, I think the problem is in the pipeline, maybe is missing from elastic, so the fields are not renamed, transformed, etc; this tutorial let you check all the steps for collecting the logs:

> **[Collecting and analyzing Zeek data with Elastic Security](https://www.elastic.co/blog/collecting-and-analyzing-zeek-data-with-elastic-security)**
>
> Learn how to ingest and analyze Zeek network data with Elastic Security and Filebeat, including how to customize your configuration specific to your objective.

---

<div class="post-metadata">

**Author:** ![test\_qweqwe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/test_qweqwe/32/94750_2.png) [@test\_qweqwe](https://discuss.elastic.co/u/test_qweqwe)\
**Post date:** [September 18, 2021, 7:55pm UTC](https://discuss.elastic.co/t/zeek-elk-integration-a-lot-of-strange-fields/284547/3 "2021-09-18T19:55:29Z")

</div>

I did everything like in this guide.  
But It didn't help.

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [September 18, 2021, 8:55pm UTC](https://discuss.elastic.co/t/zeek-elk-integration-a-lot-of-strange-fields/284547/4 "2021-09-18T20:55:00Z")

</div>

I believe all the suricata fields are showing because they're aliases of the ECS fields. I believe this has been fixed for future versions.

---

<div class="post-metadata">

**Author:** ![test\_qweqwe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/test_qweqwe/32/94750_2.png) [@test\_qweqwe](https://discuss.elastic.co/u/test_qweqwe)\
**Post date:** [September 18, 2021, 9:02pm UTC](https://discuss.elastic.co/t/zeek-elk-integration-a-lot-of-strange-fields/284547/5 "2021-09-18T21:02:23Z")

</div>

It's okay that there are a lot of fields?

---

<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:** [October 16, 2021, 11:03pm UTC](https://discuss.elastic.co/t/zeek-elk-integration-a-lot-of-strange-fields/284547/6 "2021-10-16T23:03:08Z")

</div>

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