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

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!


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