# Filebeat Fortinet Module does't parse message fields when using tcp protocol

**URL:** <https://discuss.elastic.co/t/filebeat-fortinet-module-doest-parse-message-fields-when-using-tcp-protocol/260913>\
**Category:** Beats\
**Tags:** beats-module, filebeat\
**Created:** [January 12, 2021, 10:01pm UTC](https://discuss.elastic.co/t/filebeat-fortinet-module-doest-parse-message-fields-when-using-tcp-protocol/260913 "2021-01-12T22:01:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![luigius](https://avatars.discourse-cdn.com/v4/letter/l/87869e/32.png) [@luigius](https://discuss.elastic.co/u/luigius)\
**Post date:** [January 12, 2021, 10:01pm UTC](https://discuss.elastic.co/t/filebeat-fortinet-module-doest-parse-message-fields-when-using-tcp-protocol/260913/1 "2021-01-12T22:01:29Z")

</div>

Hi everyone, I have filebeat with Fortinet module working fine if I use UDP, but when I switch to TCP stops to parse the records as Fortinet log adds at the beginning the priority (usually \<189\> or \<190\>)

Any idea on how to solve this problem?  
Any help is appreciated!

Thanks

---

<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:** [February 10, 2021, 12:01am UTC](https://discuss.elastic.co/t/filebeat-fortinet-module-doest-parse-message-fields-when-using-tcp-protocol/260913/2 "2021-02-10T00:01:36Z")

</div>

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